Is there a way to identify what a runaway thread is doing? After starting up tomcat, I put my application under heavy load for 15-20 minutes. I bring up the task manager and make sure the CPU usage is ~99 and I exercise the memory up to 140M. I check the access logs for the last request and wait for the memory to get reclaimed...it doesn't...I have finalize calls in my code.... I've waited hours after I get Tomcat in this state and there is no return to normalcy...
I get the same result using Tomcat 4.0.3 or 4.0.6.... I guess there are tools that track threads and let you know if a thread is running amuck, but is there a way to tell what it is doing?... ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
