Parse Exception in 7.2.0 SNAPSHOT when strict-max-pool uses a property value
willreichert Dec 11, 2012 9:05 AMWe are trying to use property files to tune Jboss so that we can quickly iterate our performance tests but we see an exception when trying to start Jboss with the following configuration:
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${foo:624}" instance-acquisition-timeout="1" instance-acquisition-timeout-unit="MILLISECONDS"/>
The exception we see is the folowing:
08:57:54,582 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA 08:57:54,745 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA 08:57:54,810 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting 08:57:55,339 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:305) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea] Caused by: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.asInt(ModelValue.java:58) [jboss-dmr-1.1.3.Final.jar:1.1.3.Final] at org.jboss.dmr.ModelNode.asInt(ModelNode.java:226) [jboss-dmr-1.1.3.Final.jar:1.1.3.Final] at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.parseStrictMaxPool(EJB3Subsystem12Parser.java:484) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.parseBeanInstancePools(EJB3Subsystem12Parser.java:459) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.parsePools(EJB3Subsystem12Parser.java:442) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:154) at org.jboss.as.ejb3.subsystem.EJB3Subsystem13Parser.readElement(EJB3Subsystem13Parser.java:71) at org.jboss.as.ejb3.subsystem.EJB3Subsystem14Parser.readElement(EJB3Subsystem14Parser.java:56) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:128) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:84) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1028) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:449) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:136) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 3 more
My quick reading of the EJB3Subsystem12Parser leads me to believe it supports expressions (which I assume are the variables from property files). I would certainly appriciate any help in determining if the configuration should support using properties for that attribute. Is there any way for a user to see which sections of the configuration cannot use keys from a property file?