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

UnifiedInvokerHAProxy does not implement InvokerProxyHA

    XMLWordPrintable

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      See workaround section for JBAS-5536

      Show
      See workaround section for JBAS-5536

      Description

      UnifiedInvokerHAProxy does not implement InvokerProxyHA. Because of this, ProxyFactoryHA will not update a unified invoker proxy's target list when it gets a notification of a cluster topology change. Effect is a client downloading the proxy will always get the set of targets available when the proxy was created.

      Usually the downloaded proxy will also have at least one valid target (the one for the node that created the proxy.) As soon as the client makes an invocation, the server will detect they have a stale view and piggyback the current targets with the response. So, this bug is not very likely to cause an invocation failure, but it does reduce the robustness of the proxy.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  galder.zamarreno Galder ZamarreƱo
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: