[jboss-remoting-issues] [JBoss JIRA] Created: (JBREM-1073) Allow invocations to stopped servers to throw CannotConnectExceptions

[Ron Sigal (JIRA)]

Allow invocations to stopped servers to throw CannotConnectExceptions
---------------------------------------------------------------------

                 Key: JBREM-1073
                 URL: https://jira.jboss.org/jira/browse/JBREM-1073
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP10
            Reporter: Ron Sigal
            Assignee: Ron Sigal
             Fix For: 2.2.2.SP11


org.jboss.remoting.transport.socket.SocketServerInvoker has a problem shutting down ServerThreads, which, for Remoting versions 2.4.0.GA and above, was fixed by the changes made for JBREM-821 "JBoss Remoting fails under load".  However, the problem remains in Remoting versions 2.2.x.   In particular, shutting down the SocketServerInvoker does not necessarily immediately close all if its ServerThreads.  Consequently, on the client side, it is possible for an invocation to arrive and obtain a pooled connections to the closed SocketServerInvoker, which results in org.jboss.remoting.ServerInvoker, and therefore the call to org.jboss.remoting.Client.invoke(), throwing a ServerInvoker.InvalidStateException.  This can cause problems for a clustered EJB3, leading org.jboss.invocation.unified.interfaces.UnifiedInvokerHAProxy to throw an UndeclaredThrowableException instead of trying an alternative server.

One solution seems to be to allow, as an optional behavior, org.jboss.remoting.MicroRemoteClientInvoker to translate an InvalidStateException to an org.jboss.remoting.CannotConnectException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira