-
Bug
-
Resolution: Done
-
Major
-
15.0.0.Final
-
None
The issue is that the xsd says it is using a blocking queue but it is using an incomplete bounded one since there are properties that cannot be set.
jboss-cli returns:
/subsystem=jca/workmanager=default/long-running-threads=default:read-resource-description { "outcome" => "success", "result" => { "description" => "A thread pool executor with a bounded queue where threads submittings tasks will not block. Such a thread pool has a core and maximum size and a specified queue length. When a task is submitted, if the number of running threads is less than the core size, a new thread is created. Otherwise, if there is room in the queue, the task is enqueued. Otherwise, if the number of running threads is less than the maximum size, a new thread is created. Otherwise, the task is handed off to the designated handoff executor, if one is specified. Otherwise, the task is discarded.", ...... "handoff-executor" => { "type" => STRING, "description" => "An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.", "expressions-allowed" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" }, ....
But the xsd does not allow to set a hand-off executor for the short/long running threads
The xsd:
<xs:annotation>
<xs:documentation>
<![CDATA[
See threads:blocking-bounded-queue-thread-pool.
]]>
</xs:documentation>
</xs:annotation>
- clones
-
JBEAP-15843 [GSS](7.2.z) Inconsistency in JCA Subsystem xsd, boundedqueque is used for worker threads
- Closed