2 Replies Latest reply on Nov 28, 2012 8:38 PM by ashvinmittal

    JRMPInvokerProxyHA and Failover on java.net.SocketTimeoutException: Read timed out

    ashvinmittal Newbie

      HI ,

      We are using Jboss application server version 5.1.0.GA and noticing an issue with java.net.SocketTimeoutException: Read timed out exception and JRMPInvokerProxyHA for stateless EJB remote calls.

       

      The problem is in cluster environment JRMPInvokerProxyHA fail overs to different node on socket read timeout exception we want it to fail and throw this exception back to the client.

      We are using 5 minute socket timeout configured in pooledha configuration.

       

      Here is the stack trace on debugging jboss code.

       

      java.rmi.ConnectException: Failure during invoke; nested exception is:

                java.net.SocketTimeoutException: Read timed out

                at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:659)

                at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA.invoke(JRMPInvokerProxyHA.java:224)

                at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)

                at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)

                at org.jboss.proxy.ejb.RetryInterceptor.invoke(RetryInterceptor.java:177)

                at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)

                at org.jboss.proxy.ejb.SecurityContextInterceptor.invoke(SecurityContextInterceptor.java:64)

                at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)

                at org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:118)

                at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)....

       

      Is this expected behaviour ? How can we change this ?

       

      Thanks, Ashvin