DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-08-15 08:00 --- Created an attachment (id=7830) catalina.out with full thread dump. Snipped to remove earlier startups and System.out.printlns - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-08-15 08:01 --- Bingo, the problem seems to be in a deadlock on JspServletWrappers somehow. I've attached the log of the kill -3. This was dumped inside catalina.out, and it might be interesting to notice that there had been quite a few warnings about RESETs. Leave it up to Remy to decide to reopen or not... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-08-15 11:01 --- Created an attachment (id=7832) Thread dump - reduced to 3 threads (jsp compiler,unix process,waiting jsp wrapper) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-08-15 20:07 --- That's a sync point which occurs when Jasper is in dev mode (on each access, Jasper checks for recompilation). Please read the Jasper docs (set the development init param to false in $CATALINA_HOME/conf/web.xml). I'll examine the stacktrace for a deadlock, but this particular configuration should never be put in production (it has terrible performance). Thread dumps like this are very useful info to debug contention, deadlocks, infinite loops, etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-13 08:02 --- BTW (for the one hundredth time), if Tomcat locks up and uses 100% of the CPU, you can prove your point (and likely isolate the problem) by getting a thread dump for the VM (CTRL + BREAK on Windows, kill -3 on Unix) - which thread is actually using the CPU should be quite easy to isolate. For now, I have to consider this invalid (no test case, and can't reproduce). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-08-13 07:18 --- Please submit a test case. If what you say is true, and is caused by Tomcat, then it should be reproduceable. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-27 17:02 --- Okya, but why is the 75 limit being imposed regardless of the setting of maxProcessors ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-24 11:50 --- We are seeing this same issue as well with 4.1.24 and 5.0.4alpha. We have a load test program that sends a high volume of concurrent requests to Tomcat and it consistenly refuses connections at around the 75th connection attempt. After a bit, it begins accepting connections again. We have verified that both minProcessors and maxProcessors really seem to have no effect. If you set minProcessors to say 50 or 100 and then perform a thread dump, you will see that there are not 50 pre-allocated threads. If you set maxProcessors to say 1000, you will still see failures around the 75 connection. It's also unclear why the acceptCount is limited to 128 pending connections. We have generated thread dumps and there are no deadlocks. All available threads are currently processing valid requests. The pool is simply out of threads and. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-24 12:01 --- Your test program is sending HTTP/1.1 requests, and not closing the connection, so your load tester program is bad. So until the connection timeout occurs, the processors will wait for subsequent requests. You can either: - increase the processor count to a higher value - decrease the connection timeout - set the maxKeepAliveRequests attribute to 1 on the connector, which will disable connection keepalive (that hurts performance a lot) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-09 20:52 --- We are experiencing this problem in the Tomcat 4.1.24 release. We set maxProcessors to 150 threads and still this happens after running the server for some time. Not sure why it uses up all threads and requests more. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-09 20:55 --- We are experiencing this problem in the Tomcat 4.1.24 release. We set maxProcessors to 150 threads and still this happens after running the server for some time. Not sure why it uses up all threads and requests more. I will try to get some thread dumps and post it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) --- Additional Comments From [EMAIL PROTECTED] 2003-07-09 21:03 --- You can get a thread dump by doing a kill -3 on the Java process on Unix, or using CTRL+BREAK on Windows. That should help see what the threads are doing, and see where the problem is coming from. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
