When there is already a long-running thread pool for a work manager and you try to create another one:
/subsystem=jca/workmanager=default/long-running-threads=custom:add(max-threads=30, queue-length=30)
you only get an opaque error message:
"failure-description" => "WFLYCTL0086: Failed to persist configuration change: WFLYCTL0084: Failed to marshal configuration", with a, also useless, java.lang.IllegalArgumentException in the server log.
It should be more obvious that the error is that you cannot create two long-running thread pools
To be able to check whether the long-running-threads/short-running-threads within one JCA workmanager is already defined when adding one, BoundedQueueThreadPoolResourceDefinition in threads subsystem needs to be extended to be able to check this.
- blocks
-
JBEAP-4990 Unclear error message when creating multiple thread pools of the same type for a workmanager
- Verified
- clones
-
WFCORE-1623 BoundedQueueThreadPoolResourceDefinition does not able to add additional check on the threads executor
- Resolved
- is incorporated by
-
JBEAP-5310 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha4
- Verified