[
https://issues.jboss.org/browse/AS7-6154?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-6154:
----------------------------------
Some of the subsystem declare support for expressions and the runtime service reflect the
changes accordingly, but then the XML serialisation breaks:
{noformat}
09:40:36,969 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:680) [classes.jar:1.6.0_37]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[199,21]
Message: JBAS014697: Invalid value '${core-threads:50}' for attribute
'count'
at org.jboss.as.controller.parsing.ParseUtils.invalidAttributeValue(ParseUtils.java:114)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.threads.ThreadsParser.parseScaledCount(ThreadsParser.java:820)
at org.jboss.as.threads.ThreadsParser.parseCount(ThreadsParser.java:798)
at
org.jboss.as.threads.ThreadsParser.parseBoundedQueueThreadPool1_1(ThreadsParser.java:434)
at
org.jboss.as.threads.ThreadsParser.parseBlockingBoundedQueueThreadPool(ThreadsParser.java:259)
at
org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.parseWorkManager(JcaExtension.java:423)
{noformat}
Inconsistent expression support
-------------------------------
Key: AS7-6154
URL:
https://issues.jboss.org/browse/AS7-6154
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Fix For: 7.2.0.CR1
Although some subsystem declare support for expression on certain attributes, they
actually don't support it.
As en example see datasources > pool > max-pool-size.
The DMR description says it supports expressions on this attribute:
{noformat}
"max-pool-size" => {
"type" => INT,
"description" => "The max-pool-size element specifies
the maximum number of connections for a pool. No more connections will be created in each
sub-pool",
"expressions-allowed" => true,
"nillable" => true,
"default" => 20,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
{noformat}
But then writing an expression value yields an exception
{noformat}
Request
[ERROR] {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "steps" => [{
[ERROR] "address" => [
[ERROR] ("profile" => "full"),
[ERROR] ("subsystem" => "datasources"),
[ERROR] ("data-source" => "ExampleDS")
[ERROR] ],
[ERROR] "operation" => "write-attribute",
[ERROR] "name" => "max-pool-size",
[ERROR] "value" => expression "${pool:15}"
[ERROR] }]
[ERROR] }
{noformat}
{noformat}
08:48:23,965 DEBUG [org.jboss.as.controller.management-operation]
(HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute")
failed - address: ([
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was
EXPRESSION"
{noformat}
--
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