ERXEC and locking
ERXEC and locking
- Subject: ERXEC and locking
- From: Matteo Centro <email@hidden>
- Date: Sun, 08 Jul 2012 20:55:39 +0200
Hi all,
I recently "Wonderized" a legacy WO application and I have a strange race condition that happens very rarely and only under extremely high load.
Application extends ERXApplication, Session extends ERXSession and so on, I removed all "new EOEditingContext()" and replaced them with ERXEC.newEditingContext()
but
I forgot to remove some ec.lock() and ec.unlock()
I am quite convinced that removing all locks and unlocks will bring me to a non deadlocking situation but I still want some reassurements
I read a lot of stuff and I'm here to ask to you gurus a final word on the locking rule I inferred from what I read:
If you always use ERXEC you can safely remove all lock and unlocks except for stuff that happen in background threads...
Is it true?
What about stuff that happens in session.terminate()? I would say that it should have explicit lock/unlocks but any opinions are welcome.
Thanks,
Matteo
_______________________________________________
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