Re: Confusing lock error solved, but now a restoreSessionWithID lock issue
Re: Confusing lock error solved, but now a restoreSessionWithID lock issue
- Subject: Re: Confusing lock error solved, but now a restoreSessionWithID lock issue
- From: Mike Schrag <email@hidden>
- Date: Thu, 9 Oct 2008 10:36:12 -0400
One reason why this can happen is an access to an autolocking,
coalescing ERXEC that is in that case the
session().defaultEditingContext() outside the request-response loop.
That means the unlocking code is not called (depends on the request
response loop).
I thought Mike did something to prevent that from happening, but I'm
not totally sure.
I didn't do anything on this one, though I've considered tracking the
creation Thread reference in ERXEC and throwing an exception if it's
used in any other Thread .... It's a bit draconian, though.
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