Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1106790

Summary: [GSS] (6.4.z) unbounded-queue-thread-pool keep-alive parameter doesn't work
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Aaron Ogburn <aogburn>
Component: Domain ManagementAssignee: Kabir Khan <kkhan>
Status: CLOSED NOTABUG QA Contact: Jiri Truhlar <jtruhlar>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: bbaranow, bmaxwell, brian.stansberry, dandread, istudens, jason.greene, joallen, jtruhlar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-13 15:00:19 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: 1255494    
Bug Blocks:    

Description Aaron Ogburn 2014-06-09 17:28:46 UTC 
Description of problem:

unbounded-queue-thread-pool treats all threads as core threads (core-threads inherently equals max-threads) and so they don't timeout.  Given this expected behavior, it may make more sense to not allow the keepalive-time parameter in this executor config and/or have the pool size configured through core-threads instead of max-threads (so it's clearer that all threads will be considered core threads).

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

EAP 6.3.0
Comment 6 Brad Maxwell 2016-07-13 15:00:19 UTC 
Closing as this is considered a feature not a bug: https://issues.jboss.org/browse/WFCORE-201