> From: Leon Rosenberg [mailto:[EMAIL PROTECTED] > Subject: Deadlock -> Out of Threads -> Strange Exception -> > OutOfMemory -> Server Death. > > I can't find a locked <0x61655498> entry nowhere. > But I should be able to see it to recognize the thread causing the > deadlock, shouldn't I?
I would think so. More questions: 1) Did the server exhibit any other symptoms before the apparent deadlock, such as slow response times? 2) What was the time interval between the all threads busy log entry and the OOME reports? 3) Do you have -verbose:gc or -XX:+PrintGCDetails on, or perhaps any other monitoring in place that might show the state of the heap during normal running and then leading up to the hang? 4) What are your -Xmx and PermGen size values? I'm speculating (aka grasping at straws) that a heap full situation existed for a bit before the hang, but that some code somewhere ate the OOMEs and tried to continue. - 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 unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
