Re: Cannot obtain globalId for an object failure
Re: Cannot obtain globalId for an object failure
- Subject: Re: Cannot obtain globalId for an object failure
- From: "Ricardo J. Parada" <email@hidden>
- Date: Tue, 22 Mar 2011 12:11:11 -0400
On Mar 22, 2011, at 8:50 AM, Kieran Kelleher wrote: You *should* lock in background threads.
ERXEC notificationtEC = (ERXEC) ERXEC.newEditingContext(objectStoreCollection.nextObjectStoreCoordinator());
notificationtEC.lock();
try {
// do stuff
notificationtEC.saveChanges();
} catch (Exception e) {
log.error("We had an unexpected error in background thread blah blah blah....", e);
} finally {
notificationtEC.unlock();
}
Hi Kieran,
Is this necessary for background thread if Wonder is configured with er.extensions.ERXEC.safeLocking=true ?
Or is that why you said *should* ?
:-)
Thanks, Ricardo
|
_______________________________________________
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