Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
- Subject: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
- From: Kieran Kelleher <email@hidden>
- Date: Thu, 3 Dec 2009 14:38:26 -0500
True, but then I would be bypassing the EC factory, which just seems
dirty, but yes, this very good suggestion is an elegant way to do it
for sure.
On Dec 3, 2009, at 2:16 PM, Anjo Krank wrote:
PS. And even the above is not perfect protection against an
autolock if a thread gets cpu execution delay between construction
statement and the ec.setCoalesceAutoLocks(false) statement. After
setting safelocking props to false, I should really check if the ec
was autolocked and unlock it before returning .... or even have an
ERXEC constructor that takes a safeLocking boolean param, but that
would be two more undesired constructors ....... so probably making
isLockedInThread public (or accessible using reflection) should do
the trick.
In that case, you'd be better with
return new ERXEC(os) {
public boolean useAutoLock() {return false;}
public boolean coalesceAutoLocks() {return false;}
};
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
_______________________________________________
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