Beware the BarrierController and EJBs

[jsicotte2]

Just to let the community know the use of the BarrierController to control state of HA Singletons does not work 100%. According to the wiki:

http://wiki.jboss.org/wiki/Wiki.jsp?page=HASingletonDeployer

You can use the BarrierController instead of the deploy-hasingleton directory. This is not entirely true; for JMX services it generally works, but not for EJBs. The problem is that though the stopService() methods are called on the MBeans that wrap the EJBs, the beans remain bound to JNDI an can still be called. This can cause errors in your application, especially if the EJB calls services that have been stopped.

This issue does have a bug associated with it:

http://jira.jboss.com/jira/browse/JBAS-3469

[brian.stansberry]

Thanks for reporting this.

[jsicotte2]

I have been trying to think of a way around this issue. One thing that has come to mind is to create my own BarrierController that will map JMX event x to method y. Instead of mapping JMX events to only startService() and stopSevervice().

Any other thoughts?

[mohitanchlia]

Is this bug been resolved? Few days ago we experienced the same issue. In our case it was MDB.