-
Bug
-
Resolution: Done
-
Major
-
None
-
AMQ 7.4.0.GA
-
None
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.
- relates to
-
ENTMQ-2265 document all unsupported client/broker scenarios in current image
- New