[jboss-dev-forums] [Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

[ALRubinger]

"ALRubinger" wrote : Side effect: Perhaps removal task might sneak in there and remove an instance before passivation can come along.

No, I found that both passivation and remove are synchronizing on the StatefulBeanContext instances pulled out of the cacheMap, so they're guarded there.

Additionally before passivation we check that the bean hasn't already been removed:

if (centry.getCanPassivate())

So the remaining issue is that activation does *not* synchronize on StatefulBeanContext instances, so there can be odd interleaving during passivation when a get() request comes in.

https://jira.jboss.org/jira/browse/EJBTHREE-1551

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184961#4184961

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184961