Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
A distributed-workmanager is allowed to remove its short-running-threads, but it is a required resource to a dwm and once the short-running-threads, Wildfly fails to start the dwm.
To add a distributed-workmanager:
batch
/subsystem=jca/distributed-workmanager=dwm1:add(name=dwm1)
/subsystem=jca/distributed-workmanager=dwm1/short-running-threads=dwm1:add(max-threads=11,queue-length=22)
run-batch
Remove the short-running-threads
/subsystem=jca/distributed-workmanager=dwm1/short-running-threads=dwm1:remove() { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
Then Wildfly fails to reload the dwm
12:31:34,497 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "jca"), ("distributed-workmanager" => "dwm1") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.thread.executor.short-running-threads.dwm1"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.connector.workmanager.dwm1 is missing [jboss.thread.executor.short-running-threads.dwm1]"] }
Attachments
Issue Links
- is cloned by
-
JBEAP-15581 (7.2.z) Enforce the short-running-threads requirement to a distributed workmanager
- Verified