Problem reconnecting Clients to AMQ Broker in "JBoss A-MQ 6.3 for OpenShift" high-availability configuration
Issue
- When we redeploying the broker (4 replicas) using
AMQ_SPLIT=true
(split-n directories), there is a small delay between the termination of the old POD and the new one becomes available (this are only a few seconds). In this period some requests of clients fail.
Isn'it Openshift that should handle this within the service amq-broker-tcp?
Environment
- Red Hat AMQ : 6.3.0
- OpenShift : 3.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.