Bug 998058

Summary: Unable to create or manage thread pools due to missing type definitions for blocking-bounded-queue-thread-pool and blocking-queueless-thread-pool
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: Plugin -- JBoss EAP 6Assignee: Simeon Pinder <spinder>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: urgent    
Version: JON 3.1.2CC: loleary, skondkar, spinder
Target Milestone: ER01   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 999127 (view as bug list) Environment:
Last Closed: 2014-01-02 20:33:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 999128    

Description Larry O'Leary 2013-08-16 22:15:19 UTC
Description of problem:
You can not create or manage an EAP 6 thread pool that is of one of the following types:

    blocking-bounded-queue-thread-pool
    blocking-queueless-thread-pool

Version-Release number of selected component (if applicable):
4.4.0.JON312GA

How reproducible:
Always

Steps to Reproduce:
1.  Install, configure, and start EAP 6 standalone.
2.  Start JBoss ON system.
3.  Import EAP standalone into JON inventory.
4.  Attempt to create a thread pool under the EAP standalone server of the following types (resource template drop-down):

        blocking-bounded-queue-thread-pool
        blocking-queueless-thread-pool

Actual results:
Thread pools can not be created because the target types are not available in JBoss ON.

Expected results:
These types should be visible in the resource template drop-down and on the create chilid detail page.

Additional info:
Please note that you can create these thread pools directly in EAP's management console or using jboss-cli and although they will be discovered, their configuration is invalid due to the missing thread pool types.

Comment 2 Simeon Pinder 2013-08-31 15:25:24 UTC
This is fixed with the following commit to release/jon3.1.x: e76d5a4ca28da78

This should be ready to be applied to the hotfix branch, but also needs commit from https://bugzilla.redhat.com/show_bug.cgi?id=997665 (9fd18e8) which is another issue that would stop blocking-bounded-queue-thread-pool from being created.

Moving this to MODIFIED and to be available for test in ER01.  

Larry the fixes have also been pushed to master and release/jon3.1.x, so you can verify the behavior with a recent build as well. Can you verify this behavior? Is this ready for hotfix?

Comment 3 Larry O'Leary 2013-09-16 21:19:32 UTC
Moving back to MODIFIED as this is not yet available in a build for testing.

Comment 4 Larry O'Leary 2013-09-16 21:20:16 UTC
Reassigning to spinder as he is the developer who worked this issue. I think Libor may have been assigned in error.

Comment 5 Sunil Kondkar 2013-10-07 11:57:01 UTC
Verified on Version: 3.2.0.ER2 Build Number: 9bf6f76:371eac0

Installed and imported EAP6.1 and successfully created below threadpol types
blocking-bounded-queue-thread-pool
blocking-queueless-thread-pool

These types are visible in the resource configuration template drop-down on the Create New Resource of Type [ThreadPool] page.