Re: DO NOT REPLY [Bug 12475] - CPU Usage is 0%, Tomcat doesn't response
Thank-you for your e-mail. Please note that i will be away from the office starting Wednesday June 29th, returning Thursday July 7th, with no access to email. In my absence, kindly contact Cheri Dueck at [EMAIL PROTECTED] Kind Regards, Natasha Hasmani Senior Event Manager - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 12475] - CPU Usage is 0%, Tomcat doesn't response
Thank-you for your e-mail. Please note that i will be away from the office starting Wednesday June 29th, returning Thursday July 7th, with no access to email. In my absence, kindly contact Cheri Dueck at [EMAIL PROTECTED] Kind Regards, Natasha Hasmani Senior Event Manager - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 12475] - CPU Usage is 0%, Tomcat doesn't response
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=12475. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=12475 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 12475] - CPU Usage is 0%, Tomcat doesn't response
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=12475. 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=12475 CPU Usage is 0%, Tomcat doesn't response --- Additional Comments From [EMAIL PROTECTED] 2002-10-07 20:08 --- Are you using the latest release or code from CVS ? I've seen few fixes to the thread pooling code. The traces you see are normal - there is one thread listening and a number of threads waiting ( in the thread pool ). Not sure why tomcat hungs - can you telnet to the http port or the ajp port ? ( manually ) Can you do a dump after you connect ( to see where's it hunged ) ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12475] - CPU Usage is 0%, Tomcat doesn't response
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=12475. 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=12475 CPU Usage is 0%, Tomcat doesn't response --- Additional Comments From [EMAIL PROTECTED] 2002-10-08 05:04 --- Our jars for Tomcat 3.3.1 have date: 07/12/2002. The traces are not normal. There are several waiting threads and threse is _no_ listening thread. In my message I wrote that we saw two listening threads, but they listen Ajp12 and Ajp13 ports. We removed from server.xml Ajp12 and Ajp13 and after that our server hung up without and listening thread and with several waiting threads. I found one more detail. When the server hung up I made dump with the help of jdb. I invoked the following commands: suspend and wherei all. A part from dump of hung server: ... Thread-23: MonitorRunnable: [1] java.lang.Object.wait (native method) [2] org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run (ThreadPool.java:407), pc = 11 [3] java.lang.Thread.run (Thread.java:484), pc = 11 ... What is 'Thread-23:' ? Why is there no stack trace for this thread ? There are stack traces for 'Thread-22' and 'Theread-24, but there is no for 'Thread-23'. I tried visual tools sush as IDEA and Eclipse, and I have similar result: there is a thread, which I can't suspend. I have no idea why this thread can't be suspended, but I always saw such thread, when our server hung up. We tried to find bug in your source, but we aren't familiar with your code and we didn't find anything wrong. Now we run our server under Tomcat 4.0 and we don't have such hang-up -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
