forgot to say that the simplest way to enforce that is to "notifyAll" upon a
free in the pool :)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
|Sent: Sunday, October 22, 2000 12:16 AM
|To: jBoss Developer
|Subject: RE: [jBoss-Dev] lock on home exception FIX
|
|
|yes that's it...
|
|marc
|
|
||-----Original Message-----
||From: [EMAIL PROTECTED]
||[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Oberg
||Sent: Saturday, October 21, 2000 10:52 PM
||To: jBoss Developer
||Subject: Re: [jBoss-Dev] lock on home exception FIX
||
||
||Hi!
||
||
||> Ok aaron amid his general craziness did raise a problem with the home
||> exceptions and a missing lock... yes a missplaced else, I just commited
||the
||> fix in CVS.
||>
||> Thank you aaron ;-)
||>
||> Also in there is the stuff that I saw yesterday at SUN, namely that a
||notify
||> will work better,
||
||Just a thought: the notify is only when the context is unlocked properly,
||right? If the context is either removed or thrown away due to
||exception then
||it should be notifyAll, or you will leave threads waiting for it to be
||released.
||
||/Rickard
||
||
||
||
|
|
