Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Unable to shutdown tomcat
"Thread-5" daemon prio=5 tid=7fe82c1f7000 nid=0x10c4bb000 waiting
for monitor entry [00000000] java.lang.Thread.State: BLOCKED (on
object monitor)
This thread might be a problem.
Nope - it's a daemon, so it will go away quietly when the JVM shuts down.
"AWT-AppKit" daemon prio=5 tid=7fe82f10d000 nid=0x7fff7a5b3960
runnable [00000000] java.lang.Thread.State: RUNNABLE
This thread might be a problem.
Nope - it's a daemon, so it will go away quietly when the JVM shuts down.
"main" prio=5 tid=7fe82c001800 nid=0x10448e000 runnable
[10448b000] java.lang.Thread.State: RUNNABLE at
sun.security.pkcs11.wrapper.PKCS11.C_GetSlotList(Native Method) at
sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:314) at
sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:86) at
The main thread definitely looks like it's doing something a bit odd.
Yes, this is the culprit. Since it's off in native code, it's much more
difficult to figure out what it's stuck on. The C_GetSlotList() function would
normally return immediately, so this one's very strange. If there are
additional crypto libraries installed beyond the one that ships with the JVM,
it might be hung up in one of those.
The usual entropy suspect ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
