I have an app that runs on Tomcat 7.0.21 and APR 1.4.7 just fine. The app serves both SSL and non-SSL traffic. SSL traffic makes up roughly 1% of the overall traffic. The Connectors for SSL and non-SSL both use the default value (200) for maxThreads.
When I try to run the app on Tomcat 7.0.23 (with the same server.xml, context.xml and web.xml) and APR 1.4.7, the app slowly grinds to a halt after running on a live production server for about a day. I took heap dumps of the app on both 7.0.21 and 7.0.23 and don't see any significant difference in memory usage. Memory seems to be fine. I did a stack dump on 7.0.23 when it was in its messed up state. No threads are blocked on critical sections of my app. For the port 8080 connector, there are 196 threads in "waiting on condition" and 4 threads in "runnable". For the port 8443 connector, there are 81 threads in "waiting on condition" and 119 threads in "runnable". I don't know how to interpret this data, since I'm not really clear on what the difference is between "runnable" and "waiting on condition". Do these numbers seem normal, or are they perhaps giving a clue as to what the underlying problem might be? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
