Re: Deadlock
Re: Deadlock
- Subject: Re: Deadlock
- From: WO Dev <email@hidden>
- Date: Fri, 16 Nov 2007 14:22:27 +0100
Hello Simon,
We had the same issue with an application using sharedEditingContext.
I don't know if that's your case, but on our side, removing the use
of sharedEditingContext resolved the issue.
Xavier
Hi All -
We have a deadlock problem with an app. Typically in such
situations I follow Andrew Lindesay's excellent tutorial on using
JDB to grab a thread dump off a hung instance and start digging
from there. However, with this particular deadlock JDB doesn't work
- i type "jdb -attach 8121" and then .... nothing. It just sits
there. If i then kill off the instance in another terminal the jdb
terminal springs into life saying the JVM has vanished.
I've checked I can connect to it and get a thread dump when the app
is running happily so it must be the deadlock that is causing the
problem.
Any ideas what is going wrong with JDB ? Or any advice on another
way of tracking down the deadlock ?
Thanks, Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
References: | |
| >Deadlock (From: Simon McLean <email@hidden>) |