You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/01/04 16:03:30 UTC
DO NOT REPLY [Bug 44170] New: - maxSpareThreads inoperative in http connector (under JBOSS 4.0.5?)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44170>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44170
Summary: maxSpareThreads inoperative in http connector (under
JBOSS 4.0.5?)
Product: Tomcat 5
Version: 5.5.20
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Connector:HTTP
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: faye.pearson@betfair.com
Running Tomcat in a JBOSS container.
I am having a problem where threads aren't being destroyed when there are too many idle threads:
<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector port="${tomcat.port}" address="${jboss.bind.address}"
maxThreads="500" minSpareThreads="50" maxSpareThreads="100" strategy="ms"
maxHttpHeaderSize="8192"
emptySessionPath="true"
enableLookups="false" redirectPort="${tomcat.secure.port}" acceptCount=
"100"
connectionTimeout="20000" disableUploadTimeout="true"/>
$ for host in `seq -w 1 30`; do echo $host; wget -qO -
http://exobxw$host/administration/queryjmx.jsp | grep currentThread; done
(trimmed output where the values were within expected limits)
09
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 153
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 18
11
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 315
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 27
22
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 220
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 18
23
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 185
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 18
24
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 141
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 14
25
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 188
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 18
27
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 127
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 21
28
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 247
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 15
29
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 202
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 18
30
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadCount: 242
jboss.web:name=http-0.0.0.0-8080,type=ThreadPool: currentThreadsBusy: 16
There's a bug raised in the JBOSS JIRA which has been marked as a "will not fix" because Tomcat is
using the wrong thread pool:
http://jira.jboss.org/jira/browse/JBAS-4412
Remy Maucherat [27/Nov/07 11:31 AM]
The thread pool used in that Tomcat version does not have the capability to scale back the amount of
threads used.
This used to work in an older version, I believe.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44170] - maxSpareThreads inoperative in http connector (under JBOSS 4.0.5?)
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44170>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44170
markt@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From markt@apache.org 2008-01-04 13:32 -------
This works as expected in Tomcat 5.5.25. I am not aware of this not working in a
previous Tomcat version. This looks like a JBoss issue to me.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org