Kinda looks like what happened to me. A lot of threads "waiting on condition" for no reason at all. For example:

"Thread-206" prio=1 tid=0x087b7d18 nid=0x7b88 waiting on condition [6e01e000..6e01f854]
at java.util.Stack.pop(Stack.java:59)
at org.apache.log4j.NDC.pop(NDC.java:274)


... and Stack.java looks like:

    public synchronized Object pop() {
        Object  obj;
        int     len = size(); //<===== line 59

        obj = peek();
        removeElementAt(len - 1);

        return obj;
    }

Veda N Ponnusamy wrote:
Please find attached the thread dump of the JVM. I didn't try running this app on 1.5 
jvm

Reg
Veda


-----Original Message----- From: Joseph Shraibman [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 1:26 PM To: Calvin Austin Cc: Veda N Ponnusamy; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Help on JVM hang


Calvin Austin wrote:

Does it ever resume. 1.5beta2 has more diagnostics in it and you may be able to even attached with jdb (hey tim :*)

Without seeing the other threads its difficult to see what is happening, however there was a bug fix in 1.5 to stop the cache growing out of control. A quick test with 1.5 would help a great deal.


I was never able to reproduce the hang on a test machine, it only happened in production under load. My boss would kill me if I ran a beta jvm in production.


I also haven't seen the bug for a couple of weeks since I limited the work done by that jvm in order to avoid the bug. And I'm not going to risk freezing our system in order to hit the bug again.


If I did attach to the jvm with jdb, what good would it do? What would I see that the SIGQUIT thread dump wouldn't show?


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to