Re: Let's play "Spot the Deadlock" ;-)
Re: Let's play "Spot the Deadlock" ;-)
- Subject: Re: Let's play "Spot the Deadlock" ;-)
- From: Lachlan Deck <email@hidden>
- Date: Thu, 8 Oct 2009 11:04:11 +1100
On 08/10/2009, at 8:35 AM, Kieran Kelleher wrote:
Hmmm..... not sure if it is Wonder. This is an app deployed with
Wonder source version svn#9978 (which is from Sep 27th).
There are two traces with EOObjectStoreCoordinator.lock() .... the
3rd last in my listing and that's happening in ERXEC.finalize() in
the FinalizerThread. The other is in ERXEC.objectsWithFetchSpec(...)
on a regular WorkerThread in appendToResponse in some page that I
cannot identify, not that I think it matters in this case anyway
since the finalizer is sth I have no control of ... that's the 7th
last stack trace. I am baffled as to how to resolve this one though.
Anyone WOExperts got any insight?
Has this got anything to do with your recent discussion about
transversing qualifiers for another thread? I'd be running, not
walking, to utilising a schemabased qual instead.
EOQualifier qualifier; // assume exists
EOEntity entity = EOUtilities.entityNamed(ec, entityName);
ec.rootObjectStore().lock();
try {
qualifier = entity.schemaBasedQualifier(qualifier));
}
finally {
ec.rootObjectStore().unlock();
}
newThreadProcess.setQualifier(qualifier);
with regards,
--
Lachlan Deck
_______________________________________________
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