Hello
I have the following problem with cluster: when a new cluster node starts up, session EJB3
components start to receive calls from RMI clients as soon as they are deployed, even if
the server is not started completely yet. It raises some problems for us, because some
application mechanisms are started after EJB deployment and EJBs can not process calls
properly at first time.
Is there any way to prevent clustered EJBs from receiving calls before some signal, e.g.
some Mbean starts?
Actually we are using some ugly workaround with raising special exception in AroundInvoke
interceptors and catching it on the client with some processing, but if there is better
approach, we would use it...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036965#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...