Red Hat Bugzilla – Bug 999118
Bounded thread pool creation fails due to missing required parameter queue-length
Last modified: 2013-09-04 12:08:32 EDT
This fix needs to be back-ported to the 3.1.x release.
+++ This bug was initially created as a clone of Bug #997665 +++
Description of problem:
Thread pools of type bounded-queue-thread-pool and blocking-bounded-queue-thread-pool fail to be created due to missing queue-length property which is required.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install, configure, and start EAP 6 standalone server.
2. Start JBoss ON system.
3. Import EAP 6 standalone server into inventory.
4. Configure EAP resource's connection properties.
5. Create a new *thread pool* with the minimum set of required properties for the EAP resource:
Navigate to *JBossAS7 Standalone Servers / EAP (127.0.0.1:9990)* and right-clicking on *thread > Create Child -> Thread Pool*:
*New Resource Name*: `TestBoundedPool`
*Resource Configuration Template*: `Bounded Queue Thread Pool`
*Max Threads*: `10`
Thread pool is not created and child history page reports failure with the following error message:
JBAS014746: queue-length may not be null, rolled-back=true
Queue Length should be a property value on the create wizard and the thread pool should be created successfully
I am not sure if thread pool configuration parameters have changed between versions or not so we should be careful here as I am not sure how we missed this in the original implementation.
Closing as there will be no 3.1.3 release. This is being tracked for 3.2 in 997665.