Unfortunately, I didn't know about the kill -QUIT item.
The next time the server messes up, I'll be sure to grab one of those.
That's a right useful command.
Additional information which makes me think it's a deadlock is that no
exceptions/errors occur.
The good thing about that command is that all the Threads are still
running, just waiting for some resource which is locked. If I wait an
hour to restart the server after it acts up, there could be 20+ threads
waiting for a lock, and hopefully they're all waiting for the exact same
resource.
Orion
Tore Halset wrote:
> On Feb 23, 2005, at 20:59, Orion Fields wrote:
>
>> I'm experiencing what seems to be a deadlock/synch problem with my
>> DataContexts.
>
>
> Are you able to get a stack trace of all your threads when it locks?
> It should help finding the locking point.
>
> kill -QUIT <pid>
>
> http://java.sun.com/developer/technicalArticles/Programming/Stacktrace/
>
> - Tore.
>
This archive was generated by hypermail 2.0.0 : Wed Feb 23 2005 - 16:04:58 EST