0 Replies Latest reply on Oct 24, 2008 6:09 AM by ywtsang

    ejb client cannot reconnect automatically after a network re

    ywtsang

      for normal situation, our ejb client (tomcat) can connect to jboss server successfully

      e.g.
      we have 3 jboss in clusters, we are using ejb 3 stateless session bean (clustered),
      when one jboss is down for deployment, and up again, the client can reconnect to this jboss again

      but if a network failure occurs, i.e. the client can't connect to all the 3 jbosses because our internal network is down; but when the network is recovered, the client cannot reconnect automatically, and keeps showing "Unreachable?: Service unavailable."

      it can only recovered by restarting the client (tomcat)

      (note, the jboss servers are up and running for all the time, even in network failure)




      details:

      jboss: 4.2.0-GA

      Caused by: java.lang.RuntimeException: Unreachable?: Service unavailable.
       at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:176)
       at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
       at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
       at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
       at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
       at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
       at org.jboss.ejb3.remoting.ClusteredIsLocalInterceptor.invoke(ClusteredIsLocalInterceptor.java:55)
       at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
       at org.jboss.ejb3.stateless.StatelessClusteredProxy.invoke(StatelessClusteredProxy.java:105)