Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4615 NamingContext caches stale Naming stub
  3. JBAS-4740

HARMIClient to give preference to wrapping NoSuchObjectException

    XMLWordPrintable

    Details

      Description

      HARMIClient catches a number of java.rmi exception types that indicate a request did not reach the server. It then attempts to failover, and keeps catching exceptions until all targets are exhausted. If all targets are exhausted, the last exception caught is wrapped in a RemoteException and thrown.

      This issue is to specially cache any java.rmi.NoSuchObjectException. If all targets are exhausted and an NSOE was caught, we wrap that instead of the last exception caught.

      Intent here is the NSOE provides information that a target server is listening on the given port but that the client-side naming stub is out of sync with the server-side RMI runtime. This is potentially useful to the caller; e.g. see the parent issue.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: