Bug 999127

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: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NEXTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: urgent    
Version: JON 3.1.2   
Target Milestone: ER01   
Target Release: JON 3.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 998058
: 999128 (view as bug list) Environment:
Last Closed: 2013-09-04 16:12:20 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:

Description Larry O'Leary 2013-08-20 19:07:27 UTC 
Back-port to release 3.1.x.

+++ This bug was initially created as a clone of Bug #998058 +++

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 1 Larry O'Leary 2013-09-04 16:12:20 UTC 
Closing as there will be no 3.1.3 release. This is being tracked for the 3.2 release in 997669.