-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 3/14/12 2:04 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
>> Subject: JVM won't shut down: DestroyJavaVM thread stuck on ??
> 
>> All threads are deamons except for this one:
> 
>> "DestroyJavaVM" prio=10 tid=0x00007fa528a77800 nid=0x4b2a waiting
>> on condition [0x0000000000000000] java.lang.Thread.State:
>> RUNNABLE
> 
> That's a dummy Java thread created during the shutdown processing
> to have something to do joins with.

Good to know.

> Given your symptoms, it looks like something non-Java inside the
> JVM itself is stuck.

I'm not using anything native that is specific to the app or Tomcat.
None of the stack traces I remember seeing looked suspicious.

> Does it ever break loose from this situation?

It will certainly stay stuck for several minutes. I didn't time it
from the point when I tried to shut it down until I eventually killed
the process.

The only reason I knew something was wrong was because trying to
start-up again I got an error about the connector port being
unavailable. That was weird, because Tomcat appeared to have
completely shut down, including closing its sockets.

> Is it possible that one of the daemon threads isn't actually idle, 
> but instead off doing something like waiting on a socket with 
> infinite timeout? (Although I think even that should respond to a 
> shutdown.)

That certainly is possible. If I can get it to happen again, I'll get
much better data.

Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9hFiEACgkQ9CaO5/Lv0PD29wCaA6AcvwvzOB91fo8/OuheeIe9
jtUAoMPLe9TkCcBvx7/rGd6fH0QRf8K2
=BxOj
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to