Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4963

invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • No Release
    • JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta3
    • Clustering
    • None

      Exception handling is different between JRMPInvokerProxyHA and
      UnifiedInvokerHAProxy when it comes to, at least, calls to invocationHasReachedAServer():

      1.- JRMPInvokerProxyHA

      Exception handling that does not lead to invocationHasReachedAServer() being called:

      • java.net.ConnectException
      • java.net.UnknownHostException
      • java.rmi.ConnectException
      • java.rmi.ConnectIOException
      • java.rmi.NoSuchObjectException
      • java.rmi.UnknownHostException
      • GenericClusteringException.NO

      Exception handling that leads to invocationHasReachedAServer() being called:

      • GenericClusteringException.YES
      • java.rmi.ServerException
      • java.lang.Exception

      2.- UnifiedInvokerHAProxy

      Exception handling that does not lead to invocationHasReachedAServer() being called:

      • org.jboss.remoting.CannotConnectException
      • GenericClusteringException.NO
      • java.rmi.RemoteException
      • java.lang.Throwable

      Exception handling that leads to invocationHasReachedAServer() being called:

      • GenericClusteringException.YES

      This JIRA tracks discussions to clarify the correctness of UnifiedInvokerHAProxy and any
      potential coding required.

              bstansbe@redhat.com Brian Stansberry
              rh-ee-galder Galder Zamarreño
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: