Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: JVM apparently hanging
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JVM apparently hanging




It was identical in every way except for thread id's, process id's and addresses. No deadlocks detected. Here it is in its entirety.  Thanks again for your help!

Full thread dump Java HotSpot(TM) Client VM (1.4.2-54 mixed mode):

"Thread-0" daemon prio=5 tid=0x4d20c990 nid=0x2c1afe00 runnable [f0b94000..f0b96aa0]
       at java.lang.ClassLoader$NativeLibrary.load(Native Method)
       at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
       - locked <0x510e03a8> (a java.util.Vector)
       - locked <0x510e03c0> (a java.util.Vector)
       at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
       at java.lang.Runtime.loadLibrary0(Runtime.java:788)
       - locked <0x510e03f8> (a java.lang.Runtime)
       at java.lang.System.loadLibrary(System.java:834)
       at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
       at java.security.AccessController.doPrivileged(Native Method)
       at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)
       at sun.awt.DebugHelper.<clinit>(DebugHelper.java:29)
       at java.awt.Component.<clinit>(Component.java:506)


"NotesGCThread0" daemon prio=5 tid=0x4d20c250 nid=0x2c1ab000 in Object.wait() [f0b15000..f0b15aa0]
       at java.lang.Object.wait(Native Method)
       - waiting on <0x510e0400> (a java.lang.ref.ReferenceQueue$Lock)
       at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
       - locked <0x510e0400> (a java.lang.ref.ReferenceQueue$Lock)
       at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
       at xxxxx.xxxxx.xxxxxx.NotesReferenceQueue.run(NotesReferenceQueue.java:150)
       at java.lang.Thread.run(Thread.java:552)


"Signal Dispatcher" daemon prio=10 tid=0x4d209550 nid=0x2c1a9a00 waiting on condition [0..0]

"JDWP Event Helper Thread" daemon prio=5 tid=0x4d209120 nid=0x2c1a9200 runnable [0..0]

"JDWP Transport Listener: dt_socket" daemon prio=5 tid=0x4d208e40 nid=0x2c1a8e00 runnable [0..0]

"Finalizer" daemon prio=8 tid=0x4d206af0 nid=0x2c0ccc00 in Object.wait() [f080f000..f080faa0]
       at java.lang.Object.wait(Native Method)
       - waiting on <0x510e0480> (a java.lang.ref.ReferenceQueue$Lock)
       at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
       - locked <0x510e0480> (a java.lang.ref.ReferenceQueue$Lock)
       at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
       at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)


"Reference Handler" daemon prio=10 tid=0x4d206750 nid=0x2c145600 in Object.wait() [f078e000..f078eaa0]
       at java.lang.Object.wait(Native Method)
       - waiting on <0x510e04a0> (a java.lang.ref.Reference$Lock)
       at java.lang.Object.wait(Object.java:429)
       at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
       - locked <0x510e04a0> (a java.lang.ref.Reference$Lock)


"main" prio=5 tid=0x4d200f80 nid=0xa000ed98 waiting for monitor entry [bfffb000..bfffd498]
       at java.lang.Runtime.loadLibrary0(Runtime.java:780)
       - waiting to lock <0x510e03f8> (a java.lang.Runtime)
       at java.lang.System.loadLibrary(System.java:834)
       at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
       at java.security.AccessController.doPrivileged(Native Method)
       at java.util.zip.CRC32.<clinit>(CRC32.java:25)
       at java.util.zip.ZipInputStream.<init>(ZipInputStream.java:26)


"VM Thread" prio=5 tid=0x4d205fd0 nid=0x2c0ac600 runnable

"VM Periodic Task Thread" prio=10 tid=0x4d2093c0 nid=0x2c1a9600 waiting on condition
"Exception Catcher Thread" prio=10 tid=0x4d200f20 nid=0x2c0f0600 runnable



Greg Guerin <email@hidden>
Sent by: java-dev-bounces+eric_feigenson=email@hidden

05/03/2006 01:06 PM

To
email@hidden
cc
Subject
Re: JVM apparently hanging





Eric Feigenson wrote:

>So I just did, no debugger involved. Ran the program, it hung as it always
>has, did a kill -QUIT, and the stack I get is exactly the same as it was in
>the debugger.

Was it IDENTICAL, or were there some slight differences?

In particular, were the hung threads waiting on a lock, or was one of them
suspended like it was in the debugger?

Also, did the thread-dump summary say that no deadlocks were detected, or
did it say there was one?

What other object locks were locked at the time?

Without seeing the actual thread-dump in detail, it's difficult to diagnose
anything.  I suggest posting the complete actual thread-dump (taken without
the debugger).

 -- GG


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: JVM apparently hanging (From: Greg Guerin <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.