On 23/12/2011 14:47, Christopher Schultz wrote: > Saravanan, > > 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 Seems high, as Chris says. >> Current thread count: 249 Can you post your full server.xml please, inline and with all XML comments/usernames/passwords removed. >> Current thread busy: 2 Low. >> Keeped alive sockets count: 40 Hmm? Where does that come from? >> Max processing time: 300477 ms >> Processing time: 8788.765 s Seems low for 2 hours of operation. Where does that number come from? >> Request count: 9223 >> Error count: 783 That's about 10%. What are those errors, exactly? >> Bytes received: 0.22 MB >> Bytes sent: 5.43 MB Both of those seem low for 2 hours of operation. What is your application/server doing? p > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
