Re: Deadlock [Fixed - we think!]
Re: Deadlock [Fixed - we think!]
- Subject: Re: Deadlock [Fixed - we think!]
- From: Chuck Hill <email@hidden>
- Date: Tue, 27 Nov 2007 12:26:30 -0800
On Nov 27, 2007, at 12:24 PM, Simon McLean wrote:
Hi Chuck -
Are you using the MultiECLockManager ?
A version of it.
If so are you using it with ERXEC ?
No. I don't think you would want to use both.
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.
I'd pick "get in each other's way". They are two solutions to the
same problem.
Chuck
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());
}
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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