4 Replies Latest reply on Nov 16, 2010 12:15 PM by Michael Jacobs

    Exceptions in client on cluster node shutdown

    Michael Jacobs Newbie

      In our environment we have multiple clustered JBoss AS 4.2.3.GA instances serving ejb's to clients (also running within 4.2.3.GA).  When a cluster node gets shutdown we sometimes see the following exception in the client log:

       

       

      Caused by: org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state.
              at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:820)

      Caused by: org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state.

              at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:820)

       

      Based on the timing it looks like probably the client gets the stub, then just before it's invocation, the shutting down node begins to undeploy its beans.  I am somewhat new to AS clustering, but I am guessing the stub invokes against this server since it just has not yet be notified that that node is not longer available for business.  We are using a round robin load balance policy.  My question is there any way within the framework to make the stub "try again" to another node, or should be code this ourselves.  I think using an Interceptor would be an option, but we are using EJB 2.
      Thanks, MJ