Bug 1290473 - [GSS](6.4.z) EJB thread pool keepalive not honored and is not reusing inactive threads
Summary: [GSS](6.4.z) EJB thread pool keepalive not honored and is not reusing inactiv...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Panagiotis Sotiropoulos
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-10 15:48 UTC by Brad Maxwell
Modified: 2019-10-10 10:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-24 23:39:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-3499 0 Major Open EJB thread pool keepalive not honored and is not reusing inactive threads 2018-02-19 19:13:23 UTC
Red Hat Issue Tracker JBTHR-34 0 Major Resolved Allow idle thread reusage. 2018-02-19 19:13:23 UTC
Red Hat Issue Tracker PRODMGT-1401 0 Major Resolved Fine-grained control on ejb3 thread-pool and reuse idle threads in pool before creating new 2018-02-19 19:13:23 UTC

Description Brad Maxwell 2015-12-10 15:48:10 UTC
With the default configuration below, the keepalive-time does not have any effect and it is creating a new thread on every request even when there are idle threads.

        <subsystem xmlns="urn:jboss:domain:ejb3:1.5">
            ...
            <thread-pools>
                <thread-pool name="default">
                    <max-threads count="10"/>
                    <keepalive-time time="100" unit="milliseconds"/>
                </thread-pool>
            </thread-pools>
        </subsystem>

Comment 8 Brad Maxwell 2016-03-24 23:39:38 UTC
The fix is not possible in EAP 6.4.z, the proposed fix is not safe and we will have to handle this via RFE: PRODMGT-1401 to resolve it correctly


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