Actually, I think it may have something to do with the below
question. Since the EC's I'm using are in a thread, I'm doing the
locking and unlocking manually. But I am creating them with
ERXEC.newEditingContext, and the defaultAutomaticLockUnlock flag is
true. Should I maybe be creating my thread ECs with just new
EOEditingContext?
Jeff
switched over to do the locking (and adding try/finally) and so far
so good. Are there any issues with the editingContext being created
using ERXEC and having the
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
On Mar 7, 2009, at 8:03 PM, Kieran Kelleher wrote:
IIRC, you have to do your own lock/unlock in regular background
threads ..... I always do anyway .....
ec.lock();
try {
//do stuff
} catch (Exception e) {
// handle
} finally {
ec.unlock();
}
On Mar 11, 2009, at 6:59 PM, Jeff Schmitz wrote:
I had the below messages popping up from time to time and I
discovered a place where I was disposing of an object store without
disposing of its EC first. Could that have been causing the below
errors:
Mar 11 18:52:35 netBrackets[56504] (ERXEC.java:218) ERROR
er.extensions.eof.ERXEC - Should pop, but ec not found in Vector!
Finalizer, ec: er.extensions.eof.er...@fcc032, ecs:[]
Mar 11 18:52:35 netBrackets[56504] (ERXNSLogLog4jBridge.java:43)
WARN NSLog - Exception occurred while finalizing EOEditingContext
#16564274 :null
Thanks,
Jeff
_______________________________________________
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/jeffandmonica%40mac.com
This email sent to [email protected]
_______________________________________________
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]
