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

[Rickard Oberg]

Hi!

> This lock is on the whole cache.  This means that once it is locked,
> NOBODY can enter the cache, even with a different context.  For stateful
> beans, this solution won't work since activation reads from file, for
> entity there must be a lower contention solution.

See your point. Shuold we then change so that context acquisition for
stateful do not necessarily perform the activation, so that we can do that
separately once we have the context?

I do not see any other locking solution that would provide consistent cache
usage. The locking have to be there, but we should of course minimize the
work done within that lock section.

/Rickard