A-MQ client connects to a slave broker, not the master, when Amazon ELB is in use

Solution Verified - Updated -

Issue

  • A-MQ is configured in a master-slave topology on Amazon AWS virtual machines, and
  • Amazon ELB load balancers are between the brokers and their clients, and
  • the master broker fails.
  • Clients may appear to remain connected to the slave node, not the master, but no message data can be exchanged.

Environment

  • JBoss A-MQ
    • 6.x
    • 7.x is probably affected, but this is not verified

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.