Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2709

External to OCP client access does not work for HA

XMLWordPrintable

    • AMQ Sprint 3219, AMQ Sprint 3519, AMQ Broker 3819, AMQ Broker 4219

      As per the 7.4 documentation for deploying on OCP

      External Clients that connect to a cluster of brokers, either through the OpenShift proxy or by using bind ports, may need to be configured for HA accordingly. In a clustered scenario, a broker will inform certain clients of the addresses of all the broker’s host and port information. Since these are only accessible internally, certain client features either will not work or will need to be disabled.

      At the moment we follow up with issues with the Core JMS Client and AMQP Clients. We should quantify the behaviour and limitations of the clients, clearly document what works, and raise issues to resolve against the problems found.

              jcliffor@redhat.com John Clifford
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: