]
Brian Stansberry commented on AS7-2878:
---------------------------------------
has a commit that eliminates these
properties. They were completely unused; just stored in the model.
The branch also removes the "per-cpu" configs all the "count" type
attributes (core-threads, max-threads, queue-length.) The count becomes a simple int.
It also allows expressions on those attributes and "priority".
I'm not pushing this because it will break the console. It would be good to get into
CR1 because of the expression support on those attributes, which is one of the better use
cases for expressions. But it's not critical.
Properly expose JCA pool properties
-----------------------------------
Key: AS7-2878
URL:
https://issues.jboss.org/browse/AS7-2878
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, JCA
Reporter: Heiko Braun
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
they need to be subresources:
{noformat}
[INFO] {
[INFO] "operation" => "add",
[INFO] "address" => [
[INFO] ("subsystem" => "jca"),
[INFO] ("workmanager" => "default"),
[INFO] ("short-running-threads" =>
"default-short-running-threads"),
[INFO] ("properties" => "property_name")
[INFO] ],
[INFO] "value" => "property_value",
[INFO] "boot-time" => false
[INFO] }
[ERROR] 2011-12-01 16:09:13,299 [ERROR] On Thu Dec 01 16:09:13 CET 2011, MessageCenter
received Failed: Create property property_name
[ERROR] 2011-12-01 16:09:13,300 [ERROR] Message{conciseMessage='Failed: Create
property property_name', detailedMessage='{
[ERROR] "outcome" => "failed",
[ERROR] "failure-description" => "JBAS014739: No handler for add at
address [
[ERROR] (\"subsystem\" => \"jca\"),
[ERROR] (\"workmanager\" => \"default\"),
[ERROR] (\"short-running-threads\" =>
\"default-short-running-threads\"),
[ERROR] (\"properties\" => \"property_name\")
[ERROR] ]",
[ERROR] "rolled-back" => true,
[ERROR] "response-headers" => {"process-state" =>
"reload-required"}
[ERROR] }', fired=Thu Dec 01 16:09:13 CET 2011, severity=Error, options=[]}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: