JVM hangs beyond recovery
David.Holmes at oracle.com
Sat Jun 19 22:22:20 PDT 2010
I'm afraid I can't shed any further light on this. The key is finding
out which thread holds the lock that causes the deadlock - as Ramki says
- or else determining the lock state has been corrupted.
I'm going to be away for a while, so lack of further comment is not a
sign of disinterest.
Stas Oskin said the following on 06/19/10 19:27:
> One might try truss (or Linux's strace?) to
> trace calls into libdl interfaces to see who might be taking
> out the lock (or set a watchpoint on the lock?).
> The biggest problem that this issue happens very rarely, i.e. once per
> week at most.
> AFAIK I can use strace -p to check the current situation, but I'm not
> sure how useful this information would be - as the deadlock already
> Are you running a standard version of the kernel or a non-standard
> one? (not that we can help with that; but if it's some non-standard
> kernel, you might want to talk with the appropriate linux-kernel
> alias to help find the right tools; strace should begin to shed
> some light, I am thinking.)
> I'm using the standard CentOS 5.4 kernel, the deadlock happened on
> various versions.
> The latest one (which I posted yesterday) was "2.6.18-164.9.1.el5xen",
> but it happens on later non-xen versions as well.
More information about the hotspot-runtime-dev