Hi Lachlan,
No this is nothing to do with our recent conversation :-) That
conversation is still in development. This deadlock is in a production
app that was updated 2 days ago.
Regards, Kieran
On Oct 7, 2009, at 8:04 PM, Lachlan Deck wrote:
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
