Re: Deadlock
Re: Deadlock
- Subject: Re: Deadlock
- From: Mike Schrag <email@hidden>
- Date: Fri, 16 Nov 2007 10:33:55 -0500
Is that enough to stop the shared EC being used ?
Just set er.extensions.ERXEC.useSharedEditingContext=false in your
Properties file .. That's all you need to do.
I also thought of using the LockingErrorScreamingEditingContext, but
after poking around ERXEC a little I'm not sure how to fit it in.
How would I get ERXEC.newEditingContext() to instantiate a custom EC
subclass ?
Wonder has essentially what lock screamer does built-in ... set the
debug level of the log4j category er.extensions.ERXEC.LockLogger to
DEBUG.
I also noticed ERXEC has some lock logging of it's own. I think I'll
turn that on too and see what happens.
... yes :)
ms
_______________________________________________
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