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

Update affinities on return in NamingEJBClientInterceptor

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.0.16.Final
    • 4.0.14.Final
    • None

      NamingEJBClientInterceptor allows discovering destinations for invocations based on the list of URLs in the JNDI InitialContext variable PROVIDER_URL. If the invocation has a proxy with (strong affinity, weak affinity) = (NONE, NONE), this interceptor will be used to choose a destination over DiscoveryEJBClientInterceptor.

      Like DiscoveryEJBClientInterceptor, NamingEJBClientInterceptor calls DiscoveryEJBClientInterceptor.setupSessionAffinities() to adjust affinity values in specific cases. However, whereas DiscoveryEJBClientInterceptor does this after the invocation has returned, NamingEJBClientInterceptor does it before the invocation goes out. This means that any changes to affinity made on the server are not so processed.

            rachmato@redhat.com Richard Achmatowicz
            rachmato@redhat.com Richard Achmatowicz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: