Re: ERXEC and methods getting called without lock
Re: ERXEC and methods getting called without lock
- Subject: Re: ERXEC and methods getting called without lock
- From: Anjo Krank <email@hidden>
- Date: Fri, 5 Aug 2005 14:20:43 +0200
Am 05.08.2005 um 13:45 schrieb Guido Neitzer:
On 05.08.2005, at 13:31 Uhr, Anjo Krank wrote:
b) using ERXEC as a class (ie the actual EC you get from the
factory) makes a lot of sense as it auto UNlocks after the RR loop
- which just happens and is not really under your control. You
can't use D2W without it.
But with that - it shouldn't lead to any deadlocks because of ec
locking?! Or is my logic wrong here?
Yes. A deadlock has not really much to do with left-over ECs. A real
deadlock is two actors contenting on two resources. And this can
happen quite fast if you have halfway decent traffic. Mostly, this
seems related to using the SEC to fetch things, but I'm not sure.
c) you *can* use the auto LOCK features, but I never tried it,
wouldn't recommend it and using them is generally sloppy. Fix your
code instead.
Hmm. I use it in one application and it seems to work very well.
Sure, it *might* work. But its bad practice nonetheless. And not to
mention that the EC gets locked on *every* operation, incurring a lot
of overhead.
It's more a debug and "agh, I just don´t have the time to fix this
now" kinda thing.
Cheers, Anjo
_______________________________________________
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