|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Oberg
|Sent: Friday, October 20, 2000 11:53 AM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Release lock bug in JDK?
|
|
|> then check the id upon entering the ctx lock
|>
|> if ok go on
|> if not get ctx again
|>
|> 100% safe
|
|Just an additional note: only 100% safe if we make sure that instances that
|are thrown away because of removal or exception does not have the id
|associated with the ctx. If this is not done the instance interceptor might
|get a context with the right id, although the context is invalid.
yes remember null ctx -> remove, oh man the pools are a pain, I want to get
rid of them... (because imagine someone comes and gets the context and does
"exactly" the same id)... bummer doesn't work... well sure the combined
probability of that happening is insignificant but still... really the pools
are maybe a bad idea, they complicate a lot of stuff
marc
|
|/Rickard
|
|
|
|
