-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
None
-
Workaround Exists
-
Some attributes of thread-pool (implemented in several subsystems) are nillable but cannot be undefined via the undefine-attribute operation in CLI. The operation fails even if the attribute is undefined to start with.
E.g. (truncated for brevity)
[standalone@localhost:9990 /] /subsystem=batch-jberet/thread-pool=batch:read-resource-description
{
"result" => {
"attributes" => {
"keepalive-time" => {
"type" => OBJECT,
"nillable" => true,
"value-type" => {
"time" => {
"type" => LONG,
"nillable" => false
},
"unit" => {
"type" => STRING,
"nillable" => false
}
}
},
"thread-factory" => {
"type" => STRING,
"nillable" => true,
"restart-required" => "all-services"
}
}
}
}
[standalone@localhost:9990 /] /subsystem=batch-jberet/thread-pool=batch:undefine-attribute(name=keepalive-time)
{
"outcome" => "failed",
"failure-description" => "WFLYTHR0029: Missing 'time' for 'keepalive-time'",
"rolled-back" => true
}
The attributes can be manually deleted in standalone.xml without it breaking anything (as far as I can tell) so I assume this is incorrect behavior.
Furthermore if you undefine e.g. the thread-factory first, thus putting the server in a reload-required state, then keepalive-time can be undefined without the previous error being thrown.
- is depended on by
-
-
- Resolved
-
