Re: Confusing locking error
Re: Confusing locking error
- Subject: Re: Confusing locking error
- From: Guido Neitzer <email@hidden>
- Date: Wed, 8 Oct 2008 09:53:08 -0600
On 08.10.2008, at 09:26, Simon McLean wrote:
I've bolded the lines that are of interest. It's saying that it
attempted to lock an editing context in a method called
trainlineTicketTypes, but the ec was previously locked in a method
called buildNewHotelProfile. The thing that's stumped me is both
these methods use brand new ERXEC's via ERXEC.newEditingContext().
The one inside the long response is explicitly locked and unlocked
in a try / catch / finally block, the other one is left to ERXEC
autolocking.
Haven't looked what's really going on in the traces, but the "normal"
mistake on these pages is that you access something (accessing also
means localInstanceOf - you need to do that differently, e.g. with
passing in global ids) that doesn't belong to your thread.
cug
--
Real World WebObjects Bootcamp at the Big Nerd Ranch:
http://www.bignerdranch.com/classes/real-world_webobjects.shtml
_______________________________________________
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