Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-17 Thread Roger Keays
I've studied a number of stack traces and the locking seems fine - there is evidence of cyclical deadlock. The problem is that a whole lot of threads (including the ones holding the locks) are listed as 'waiting for monitor' but I can't see why. I found out that it was the garbage collector

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-17 Thread Roger Keays
Leon Rosenberg wrote: This is called thread hi-jacking :-) Sorry, thought it might be the same issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-17 Thread Roger Keays
Hi Leon, Thanks for your tip about the NPTL threads. I tried upgrading to linux 2.6.8 and glibc 2.3.5, but the problem remains :( I've studied a number of stack traces and the locking seems fine - there is evidence of cyclical deadlock. The problem is that a whole lot of threads (including

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-17 Thread Leon Rosenberg
This is called thread hi-jacking :-) However, without knowing anything about your jdo implementation I can't say if org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:645) - waiting to lock <0x5b775de0> (a and TP-Processor17" daemon prio=1

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-16 Thread Roger Keays
Hi Leon, Recently I've noticed similar deadlocks on my tomcat server. In my case, the server just hangs with no warning even though there is plenty of memory available. I tried the following to locate the problem, but it has all been in vain: * upgrade jdk from 1.5.0.1 to 1.5.0.6 *

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-16 Thread Leon Rosenberg
Update: between the memory leakage started approx. at 20:15 and reached the end of the bottle at 21:10 with 40 Mb free memory. At this time the server started to loose users. Until 21:45 it droped about 1000 users leaving 21 on the server, before it got restarted at 21:50 as I stated in the previo

Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-15 Thread Leon Rosenberg
On 3/15/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > 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 i

RE: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-15 Thread Caldarale, Charles R
> 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 wou

Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

2006-03-15 Thread Leon Rosenberg
Hi, I analyzed my thread dump and log files from yesterdays's crash a bit. Here the flow of events: First probably the deadlock occured. The following entry in logfiles is an indication for it: Mar 14, 2006 8:53:03 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (750) ar