Bug 1320680 - [GSS](6.4.z) Admin and Config Guide: EJB3 Subsystem thread-pool configuration - remove keepalive-time and clarify max-threads
Summary: [GSS](6.4.z) Admin and Config Guide: EJB3 Subsystem thread-pool configuration...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: post-GA
: ---
Assignee: David Michael
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 17:37 UTC by Brad Maxwell
Modified: 2019-10-10 11:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-20 19:12:23 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-3943 0 Critical Verified Docs: Missing EJB3 Subsystem thread-pool configuration 2016-11-02 07:01:05 UTC

Description Brad Maxwell 2016-03-23 17:37:52 UTC
Document URL: 

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Configuring_EJB_Thread_Pools

        <subsystem xmlns="urn:jboss:domain:ejb3:1.5">
            ...
            <async thread-pool-name="default"/>
            <timer-service thread-pool-name="default" default-data-store="default-file-store">
             ...
            <remote connector-ref="remoting-connector" thread-pool-name="default"/>
            <thread-pools>
                <thread-pool name="default">
                    <max-threads count="10"/>
                    <keepalive-time time="100" unit="milliseconds"/>
                </thread-pool>
            </thread-pools>
            ...
        </subsystem>


Section Number and Name: 

Describe the issue: 

keepalive-time should be removed as it is not actually used, as the thread pool created sets core threads = max threads, thus the max-threads is the max # of threads but effectively the # of threads, meaning the threads pool will create threads a thread on every request until it reaches max and then remain there.  Even if there is only 1 concurrent client such that there are free threads in the pool, it will still create them until hitting max.

Suggestions for improvement: 

Additional information:

Comment 2 JBoss JIRA Server 2016-04-20 10:33:11 UTC
Romain Pelisse <belaran> updated the status of jira JBEAP-3943 to Coding In Progress

Comment 5 JBoss JIRA Server 2016-06-16 11:18:26 UTC
David Michael <dmichael> updated the status of jira JBEAP-3943 to Coding In Progress

Comment 6 JBoss JIRA Server 2016-07-07 15:34:36 UTC
Martin Simka <msimka> updated the status of jira JBEAP-3943 to Reopened

Comment 7 JBoss JIRA Server 2016-07-08 06:45:00 UTC
David Michael <dmichael> updated the status of jira JBEAP-3943 to Coding In Progress

Comment 8 sgilda 2016-09-15 15:06:31 UTC
This topic needed more cleanup. 

The keep-alive element was commented out instead of being removed and was still appearing in the rendered documentation. Also, other references to 'keep-alive' needed to be removed.


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