January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2595) Jars in root of a sar archive not added to the sar's classpath

by Mike Clark (Created) (JIRA)

Jars in root of a sar archive not added to the sar's classpath -------------------------------------------------------------- Key: AS7-2595 URL: https://issues.jboss.org/browse/AS7-2595 Project: Application Server 7 Issue Type: Bug Components: Deployment Affects Versions: 7.1.0.Final Reporter: Mike Clark Assignee: Thomas Diesler In previous versions, a sar archive includes classes in the sar archive's root on the sar's classpath. It is quite common to have a structure such as: mbean.sar ├── some.jar └── META-INF ├── jboss-service.xml └── MANIFEST.MF However, this does not work. The classes in some.jar are not available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] (AS7-3165) Admin console: inappropriate way of selecting a Cache Type for a Security Domain

by Jan Martiska (Created) (JIRA)

Admin console: inappropriate way of selecting a Cache Type for a Security Domain -------------------------------------------------------------------------------- Key: AS7-3165 URL: https://issues.jboss.org/browse/AS7-3165 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Attachments: cachetype.png See screenshot. The field for selecting Cache Type should rather be a listbox instead of plain input text, as it is said to accept only two possible values ('default' and 'infinispan'). It is currently possible to enter a value different from 'default' or 'infinispan', and the operation will succeed!!! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

7
8
0 / 0

[JBoss JIRA] (AS7-3164) Admin console: Conditional port assignment in socket binding group incorrectly shown as number -1

by Jan Martiska (Created) (JIRA)

Admin console: Conditional port assignment in socket binding group incorrectly shown as number -1 ------------------------------------------------------------------------------------------------- Key: AS7-3164 URL: https://issues.jboss.org/browse/AS7-3164 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Attachments: socketbinding.png Screenshot says it all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
7
0 / 0

[JBoss JIRA] (AS7-3168) Admin console: issues with creation of system properties

by Jan Martiska (Created) (JIRA)

Admin console: issues with creation of system properties -------------------------------------------------------- Key: AS7-3168 URL: https://issues.jboss.org/browse/AS7-3168 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Admin console doesn't currently verify the property's name when creating a system property. The creation will fail when it is sent to server, it should fail in the console itself, because console can verify if property's name is invalid. Server side failure should only occur when a property with the same name already exists. Furthermore, it seems that in some scenarios, when you use an invalid name of a system property, for example containing some national characters, such as ěščžěščřěščř, the system property WILL get created (and will exist on the server), but the admin console will be UNABLE to show any of the existing system properties - when you navigate to system property page, it will show an empty table!!!! This will require deleting this property using CLI before system property management can be used in admin console again. NOTE: other than system properties, this applies to OSGi framework properties and most likely more property types as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

7
10
0 / 0

[JBoss JIRA] (AS7-3169) Admin console: missing validation on JVM arguments

by Jan Martiska (Created) (JIRA)

Admin console: missing validation on JVM arguments -------------------------------------------------- Key: AS7-3169 URL: https://issues.jboss.org/browse/AS7-3169 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung Priority: Critical Attachments: jvmargs.png It is currently possible to set invalid JVM arguments for a server instance or group, as seen in the attached screenshot. The input field designating heap size and maximum heap size should be somehow reworked, made more intuitive, at least the help should show more information on what you can put in. If you enter an invalid value, the operation will succeed, the invalid value will be used after the domain is restarted, and causing related servers to NOT BOOT UP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
7
0 / 0

[JBoss JIRA] (AS7-3179) Admin console: missing "Edit" button for EJB3 thread pools

by Jan Martiska (Created) (JIRA)

Admin console: missing "Edit" button for EJB3 thread pools ---------------------------------------------------------- Key: AS7-3179 URL: https://issues.jboss.org/browse/AS7-3179 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Dustin Kut Moy Cheung in standalone mode, navigate to Profile/Profile/Container/EJB 3/Thread pools. it used to be possible to edit an existing thread pool using a button, however in the latest snapshot, as of 4th January, I can't find it anymore. Nor can the selenium testsuite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
5
0 / 0

[JBoss JIRA] (AS7-3364) Admin console allows assigning multiple connectors to the same socket binding

by Jan Martiska (JIRA)

Jan Martiska created AS7-3364: --------------------------------- Summary: Admin console allows assigning multiple connectors to the same socket binding Key: AS7-3364 URL: https://issues.jboss.org/browse/AS7-3364 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor When creating a connector, the form checks that the value "Socket Binding" does not reference a socket binding that is already taken by another connector. If it is taken, validation of the form fails. However, when you successfully create a server and then CHANGE the Socket Binding using the 'Edit' button, this validation is not applied. Therefore it is possible to assign two different connectors to the same socket binding, e.g. to the same port. This will cause a "java.lang.Exception: Socket bind failed: [98] Address already in use" when the server is restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] (AS7-3367) Admin console should not allow setting min-pool-size for datasources greater than max-pool-size

by Jan Martiska (JIRA)

Jan Martiska created AS7-3367: --------------------------------- Summary: Admin console should not allow setting min-pool-size for datasources greater than max-pool-size Key: AS7-3367 URL: https://issues.jboss.org/browse/AS7-3367 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Attachments: poolsizes.png I think the title says everything. See screenshot. Concerns both Regular Datasources and XA Datasources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
4
0 / 0

[JBoss JIRA] (AS7-3412) Unable to add ejb3 thread pool

by Jan Martiska (JIRA)

Jan Martiska created AS7-3412: --------------------------------- Summary: Unable to add ejb3 thread pool Key: AS7-3412 URL: https://issues.jboss.org/browse/AS7-3412 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Fix For: 7.1.0.Final In the latest update, ejb3 thread pools now require specifying the time unit for keepalive-time, until now, it has only been a simple number, now it is an object. Trying to create an ejb3 thread pool in admin console will fail: { "outcome" => "failed", "failure-description" => "Attribute keepalive-time expects values of type OBJECT but got 100 of type INT", "rolled-back" => true } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1758) CLI usability: operations need conventient help option too

by Radoslav Husar (JIRA)

CLI usability: operations need conventient help option too ---------------------------------------------------------- Key: AS7-1758 URL: https://issues.jboss.org/browse/AS7-1758 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Alexey Loubyansky Priority: Critical This is a critical usability issue. We must provide a way to get help about operations usage too. Its difficult to comprehend how to use operations from this model: {code} [domain@localhost:9999 /] :read-operation-description(name="upload-deployment-url") { "outcome" => "success", "result" => { "operation-name" => "upload-deployment-url", "description" => "Indicates that the deployment content available at the included URL should be added to the deployment content repository. Note that this operation does not indicate the content should be deployed into the runtime.", "request-properties" => {"url" => { "type" => STRING, "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", "required" => true, "min-length" => 1, "nillable" => false }}, "reply-properties" => { "type" => BYTES, "description" => "The hash of managed deployment content that has been uploaded to the domain's or standalone server's deployment content repository.", "min-length" => 20, "max-length" => 20, "nillable" => false } } } [domain@localhost:9999 /] {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012