RE: [jBoss-Dev] Release lock bug in JDK?

[Bordet, Simone]

Hey Sebastien,

> Hi,
> 
> This lock is on the whole cache.  

What do you mean exactly ? It seems to me that this lock is not on the
cache, and it is unlocked as soon as it is not needed.

> This means that once it is locked,
> NOBODY can enter the cache, even with a different context.  

This is a statement or a wish ?

> For stateful
> beans, this solution won't work since activation reads from file, 

Do not follow... For stateful this solution degenerates in the
synchronization statement where the sync object is the instance cache; the
activation is synchronous with the call to the cache (ie if the object has
to be activated, the instance int'r waits) ? May you expand ?

> for
> entity there must be a lower contention solution.

It seems to me that the contention is low, since this lock is released ASAP.
Did you find any problem with it ? Am I missing something ?

Best Regards,

Simon