January 2013 - jboss-jira - Jboss List Archives

[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

11 years, 3 months

1
0
0 / 0

[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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5145) Expansion of variables in infinispan subsystem in standalone.xml doesn't work

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-5145?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz updated AS7-5145: ------------------------------------- Fix Version/s: 7.2.0.Alpha1 > Expansion of variables in infinispan subsystem in standalone.xml doesn't work > ----------------------------------------------------------------------------- > > Key: AS7-5145 > URL: https://issues.jboss.org/browse/AS7-5145 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Reporter: Ondrej Nevelik > Assignee: Richard Achmatowicz > Fix For: 7.2.0.Alpha1 > > > The value of "${jboss.node.name}" system property would be really useful when defining a cache(especially cache-store) in urn:jboss:domain:infinispan:1.3 subsystem. Currently the variables are not expanded. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5145) Expansion of variables in infinispan subsystem in standalone.xml doesn't work

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-5145?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz resolved AS7-5145. -------------------------------------- Resolution: Done > Expansion of variables in infinispan subsystem in standalone.xml doesn't work > ----------------------------------------------------------------------------- > > Key: AS7-5145 > URL: https://issues.jboss.org/browse/AS7-5145 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Reporter: Ondrej Nevelik > Assignee: Richard Achmatowicz > Fix For: 7.2.0.Alpha1 > > > The value of "${jboss.node.name}" system property would be really useful when defining a cache(especially cache-store) in urn:jboss:domain:infinispan:1.3 subsystem. Currently the variables are not expanded. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5145) Expansion of variables in infinispan subsystem in standalone.xml doesn't work

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-5145?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-5145: ------------------------------------------ As of AS 7.2.0, expressions can now be used in almost all attributes of cache store elements. In particular, they can be used as in the example above. > Expansion of variables in infinispan subsystem in standalone.xml doesn't work > ----------------------------------------------------------------------------- > > Key: AS7-5145 > URL: https://issues.jboss.org/browse/AS7-5145 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Reporter: Ondrej Nevelik > Assignee: Richard Achmatowicz > > The value of "${jboss.node.name}" system property would be really useful when defining a cache(especially cache-store) in urn:jboss:domain:infinispan:1.3 subsystem. Currently the variables are not expanded. -- 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

11 years, 3 months

1
0
0 / 0

[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

11 years, 3 months

1
0
0 / 0

[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

11 years, 3 months

1
0
0 / 0

[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: ---------------------------------- Assignee: Tomek Adamski > 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 > > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6413) Remove subsystem command in JGroups management api should remove existing stacks.

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-6413?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-6413: ------------------------------------------ Implemeted the change in the model stage of JGroupsSubsystemRemove: if there are existing stacks defined, prepare and execute operations to remove the stacks before finally removing the subsystem itself. > Remove subsystem command in JGroups management api should remove existing stacks. > --------------------------------------------------------------------------------- > > Key: AS7-6413 > URL: https://issues.jboss.org/browse/AS7-6413 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.2.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 7.2.0.Alpha1 > > > The management command > {noformat} > /subsystem=jgroups:remove() > {noformat} > should check for existing stack children and remove their runtime services before removing its own runtime services. > Otherwise removing the JGroups subsystem, followed by adding it back in and creating a new stack with the same name will fail due to duplicate MSC services associated with the stack. > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6412) Transformation logging issues

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6412?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on AS7-6412: ---------------------------------- that "subsystem 'infinispan' model version 'null'" is problem with tests not with actual runtime, but need to be addressed in any case. > Transformation logging issues > ----------------------------- > > Key: AS7-6412 > URL: https://issues.jboss.org/browse/AS7-6412 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > Kind of a grab bag dumping ground for issues I've noted with the new transformation logging stuff. > Here's an example message I saw posted in an unrelated discussion: > subsystem 'infinispan' model version 'null' -- attributes null JBAS014886: are not understood in that model version and this resource will need to be ignored on that host. > I'm not sure about the model version 'null' bit. Maybe that was a dev error, or perhaps a bug. If there are valid cases for 'null' there the logic needs to account for that and output something nicer. > The "attributes null" bit: we need to deal with cases where no attribute names are passed in. (There are cases like this.) If that happens the entire "attributes xxx" bit should be skipped. > The message param passed in is going to be an i18n message, so the message structure should account for that and not try to assume some particular English grammar. For example > Subsystem 'infinispan' model version '1.2.3' -- attribute(s) abc, def had the following problem: JBAS014886: Attributes are not understood in that model version and this resource will need to be ignored on that host. -- 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

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2013