tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Ruthenbeck <>
Subject Re: HttpProcessor not freeing back to pool
Date Wed, 28 May 2003 19:02:49 GMT

Each of the HttpProcessor's are separate Threads running in the JVM, so 
something is hanging (most likely in your code) and never returning the 
Processor to the pool.  Try getting a Thread dump (Ctrl-Brk) and see where 
these threads are hanging at ... it'll probably be obvious from that.


At 07:07 AM 5/28/2003, you wrote:

>We've started having a problem with HttpProcessors not being freed up. We're
>runing tomcat in standalone mode and it starts up fine and creates about 28
>HttpProcessor threads and runs for several days without any problems, then
>we see this in the catalina_log:
>2003-05-27 16:09:38 HttpProcessor[443][29] Starting background thread
>2003-05-27 16:09:42 HttpProcessor[443][30] Starting background thread
>2003-05-27 16:09:48 HttpProcessor[443][31] Starting background thread
>[skipping the same log message for threads 32 to 146]
>2003-05-27 16:34:45 HttpProcessor[443][147] Starting background thread
>2003-05-27 16:35:02 HttpProcessor[443][148] Starting background thread
>2003-05-27 16:35:11 HttpProcessor[443][149] Starting background thread
>2003-05-27 16:35:11 HttpConnector[443] No processor available, rejecting
>this connection
>2003-05-27 16:35:11 HttpConnector[443] No processor available, rejecting
>this connection
>2003-05-27 16:35:11 HttpConnector[443] No processor available, rejecting
>this connection
>[and so on...]
>And then the connections keep getting rejected until we restart tomcat.
>There is nothing interesting in the access or error logs around the time
>shown in the catalina log. I don't know if it's relevant, but you'll note
>that this is on an SSL connector.
>I don't think that its a performance or tuning or load issue because it
>never resolves on it's own (and we've left it running for several hours). It
>looks like something happens that causes HttpProcessors to stop being
>released back into the pool.
>I've searched the web, usenet, this mailing list, and the tomcat bugs DB so
>I know that questions similar to this one come up from time to time and I've
>read all the related information but it hasn't helped. So any additional
>information would be helpful.
>Also, I'll take the novel approach and assume that the error might lie in my
>code and ask if there are any things that servlets can do that would cause
>the HttpProcessor to not be released? (I naively assumed that there were
>various timeouts that would release the HttpProcessors even in the case of
>monumental stupidity on the part of the servlet programmer.)
>For more information, I'm running Windows 2000 Server, tomcat 4.1.21, and
>java 1.3.1_07. And here's the connector part of my server.xml:
>     <Connector className="org.apache.catalina.connector.http.HttpConnector"
>                port="443" minProcessors="5" maxProcessors="150"
>                enableLookups="true"
>                acceptCount="10" debug="0" scheme="https" secure="true">
>       <Factory className=""
>                clientAuth="false" protocol="TLS"
>                keystoreFile="C:/webressecure/tomcat_keystore"
>     </Connector>
>Bill Tomlinson
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Justin Ruthenbeck
Software Engineer, NextEngine Inc.
justinr - AT - nextengine DOT com

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message