[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-6425:
-------------------------------------
Summary: Imposible to define attribute via web administration console as system property expression
Key: AS7-6425
URL: https://issues.jboss.org/browse/AS7-6425
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.2.0.Alpha1
Reporter: Ondřej Chaloupka
Assignee: Brian Stansberry
What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
{code}
${some.variable:5000}
{code}
the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
The change is not propagated (not saved) to xml config file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Ondřej Chaloupka updated AS7-6424:
----------------------------------
Description:
In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
This was hit on ejb subsystem.
You can try to set following tag like this
{code}
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
{code}
In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
was:
In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
This was hit on ejb subsystem.
You can try to set following tag like this
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6424:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6424:
----------------------------------
Assignee: Heiko Braun (was: Brian Stansberry)
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-6424:
-------------------------------------
Summary: Web administration console does not handle values set with expressions
Key: AS7-6424
URL: https://issues.jboss.org/browse/AS7-6424
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.2.0.Alpha1
Reporter: Ondřej Chaloupka
Assignee: Brian Stansberry
In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
This was hit on ejb subsystem.
You can try to set following tag like this
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBREM-1182) Update testsuite to run under Hudson
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JBREM-1182?page=com.atlassian.jira.plugin... ]
Richard Achmatowicz resolved JBREM-1182.
----------------------------------------
Resolution: Out of Date
> Update testsuite to run under Hudson
> --------------------------------------
>
> Key: JBREM-1182
> URL: https://issues.jboss.org/browse/JBREM-1182
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: general
> Affects Versions: 2.2.3.SP1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 2.2.4.SP1
>
> Attachments: JBREM-1182-JRunit.patch, JBREM-1182.patch
>
>
> Update the JBoss Remoting testsuite to run under Hudson. Some current problems include:
> (i) on Linux, JRunit based tests are failing due to members not finding each other
> (ii) on Linux, under JDK6, JRunit based tests are not able to create a JGroups stack
> (iii) JRunit system properties specified by the user on the command line are not being passed the the JUnit targets correctly, and so have no effect on the tests
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-2595) Jars in root of a sar archive not added to the sar's classpath
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-2595?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-2595:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> 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: JMX
> Reporter: Mike Clark
> Assignee: Tomek Adamski
> Fix For: 7.2.0.Alpha1
>
>
> 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
> mbean.sar/META-INF
> mbean.sar/META-INF/jboss-deployment-structure.xml
> mbean.sar/META-INF/jboss-service.xml
> mbean.sar/META-INF/MANIFEST.MF
> mbean.sar/some.jar
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months