Hi Chuck -
Are you using the MultiECLockManager ? If so are you using it with
ERXEC ? And if so are you using it in conjunction with Wonder's auto-
lock management, or do you have that switched off ?
Before we started using Wonder we used MultiECLockManager, then we
kind of used both, but now we have dropped MultiECLockManager and
rely on Wonder's auto-locking. I was never quite sure if Wonder and
MultiECLockManager completmented each other, or got in each other's way.
Simon
On 27 Nov 2007, at 18:02, Chuck Hill wrote:
For reference, here is my terminate method:
public void terminate()
{
// Need to make sure this is unlocked so that editing
contexts nested in the defaultEditingContext
// don't hold locks on it when it gets disposed
synchronized (ecLockManager)
{
if (ecLockManager().isLocked())
{
try
{
ecLockManager().unlock();
}
catch (Throwable t)
{
// DANGEROUS: we *must* eat this exception or the
whole app might deadlock
NSLog.err.appendln("********** EXCEPTION in
WOSession.terminate() calling ecLockManager.unlock(): " + t);
}
}
}
super.terminate();
NSLog.out.appendln("Terminated session " + sessionID());
NSLog.out.appendln("Remaining active sessions: " +
WOApplication.application().activeSessionsCount());
}
_______________________________________________
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]
