> From: Peter Crowther [mailto:[EMAIL PROTECTED] > Subject: RE: jvm cowardly refuses to print a thread dump > > Might the code have ended up with all threads stuck in OS > calls? It feels a little unlikely, as I assume the JVM keeps > a couple of threads for itself...
Unlikely that everybody's off in native code. The JVM uses quite a few threads internally, only some of which show up in a JVM-produced thread dump. There is a Signal Dispatcher thread, so if that one got stuck someplace, I would expect signals to not get processed in a timely fashion. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
