Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-32

EJB client implementation doesn't take into account undeployment notification time lag while handling invocations

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.5.Final, 1.1.0.Alpha1
    • 1.0.4.Final
    • None

      The issue is explained in detail at AS7-3828. The current design/implementation of EJB client API can cause a node being selected for handling invocations even though the application might have been undeployed from that node. The EJB client API implementation should retry that invocation on a different node, if it fails with a NoSuchEJBException.

              jaikiran Jaikiran Pai (Inactive)
              jaikiran Jaikiran Pai (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: