> > and just lock on the context since at least it seems > > that it does > > release locks on the object it has. > > ideas? (btw the test code is in jbosstest and is called "locktest" > > I'd suggest to use the instance cache object also for wait and notifyAll > instead of the context. Since the logic for wait and notifyAll is in the > int'rs and they all can access the container, they all can access the > instance cache. Works but would be too slow. Too many threads waking up to see "oh, it was not for me". Nah, the semaphore stuff I submitted should work better. /Rickard
- RE: [jBoss-Dev] Release lock bug in JDK? Fixed ? Bordet, Simone
- RE: [jBoss-Dev] Release lock bug in JDK? Fixed ? Rickard Oberg
- RE: [jBoss-Dev] Release lock bug in JDK? Fixed ? Bordet, Simone
- Re: [jBoss-Dev] Release lock bug in JDK? Fixed ? Rickard Oberg
- RE: [jBoss-Dev] Release lock bug in JDK? Fixed... marc fleury
- Re: [jBoss-Dev] Release lock bug in JDK? F... Rickard Oberg
- RE: [jBoss-Dev] Release lock bug in J... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- RE: [jBoss-Dev] Release lock ... marc fleury
- Re: [jBoss-Dev] Release lock ... Rickard Oberg
- RE: [jBoss-Dev] Release lock ... marc fleury
- RE: [jBoss-Dev] Release lock ... marc fleury
