Bug 1106790 - [GSS] (6.4.z) unbounded-queue-thread-pool keep-alive parameter doesn't work
Summary: [GSS] (6.4.z) unbounded-queue-thread-pool keep-alive parameter doesn't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kabir Khan
QA Contact: Jiri Truhlar
Russell Dickenson
URL:
Whiteboard:
Depends On: 1255494
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-09 17:28 UTC by Aaron Ogburn
Modified: 2018-12-09 17:58 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-13 15:00:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-201 0 Major Resolved UnboundedQueueThreadPool's keep-alive param is currently useless 2019-03-08 11:37:16 UTC

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


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