|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Oberg
|Sent: Thursday, October 19, 2000 10:55 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Release lock bug in JDK?
|
|
|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?
yes absolutely, that is what I recommended in my previous mail.
In fact it is the way it is done for entity ("state synchronization" is done
in another interceptor) the state "activation" for stateful does read and
that can be slow.
|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.
yes
marc
|
|/Rickard
|
|
|
|
