tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat HTTPS Connector Stops working after an hour
Date Fri, 23 Dec 2011 14:47:48 GMT
Hash: SHA1


On 12/23/11 7:03 AM, Saravanan L wrote:
> Please find the latest thread dump attached with mail.
> Tomcat 7 still crashes without acceptCount.  I am wrong on this
> assumption.
> The response code is 504. It takes about 2 hours for this occur.
> The last status in http-apr-443 (In Server status ) is : Max
> threads: 5000 Current thread count: 249 Current thread busy: 2 
> Keeped alive sockets count: 40 Max processing time: 300477 ms
> Processing time: 8788.765 s Request count: 9223 Error count: 783
> Bytes received: 0.22 MB Bytes sent: 5.43 MB

What happens if you configure your HTTPS connector with fewer max
threads, say, 50? Does the connector lock-up more quickly? What does
your load profile look like? Is this observable in a testing
environment or only in production? If you could set up a simple jmeter
test against a test webapp, that would be ideal for trying to debug
this issue.

If you switch to NIO or BIO connector, does Tomcat become more stable,
or do you experience the same phenomenon?

- -chris
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with Mozilla -


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

View raw message