Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1106790 - [GSS] (6.4.z) unbounded-queue-thread-pool keep-alive parameter doesn't work
[GSS] (6.4.z) unbounded-queue-thread-pool keep-alive parameter doesn't work
Status: CLOSED NOTABUG
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management (Show other bugs)
6.3.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kabir Khan
Jiri Truhlar
Russell Dickenson
:
Depends On: 1255494
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-09 13:28 EDT by Aaron Ogburn
Modified: 2016-07-13 11:00 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-13 11:00:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFCORE-201 Major Resolved UnboundedQueueThreadPool's keep-alive param is currently useless 2018-05-17 09:30 EDT

  None (edit)
Description Aaron Ogburn 2014-06-09 13:28:46 EDT
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 11:00:19 EDT
Closing as this is considered a feature not a bug: https://issues.jboss.org/browse/WFCORE-201

Note You need to log in before you can comment on or make changes to this bug.