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

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.