We have this configuration: - AMQ 4.1.2 - Client outside of a firewall. Uses FailoverTransport to connect to brokers. - Two brokers inside of firewall in master/slave configuration
Problem: Upon startup, if the client attempts to connect to the slave broker instead of the master broker, the firewall ends up spoofing the client into thinking the connection was successful to the broker. But in reality what happens is the connection to the firewall succeeds and the client sends connectionInfo and waits for response. The firewall then attempts to connect to the slave, connection fails and after a period of time the firewall resets the connection back to the client. However, by the time this happens the client is already hung waiting for a response. Questions: - Has anyone experienced this problem and found a workaround? - Does this problem still exist in AMQ 5.x? Regards, Rob -- View this message in context: http://www.nabble.com/AMQ-4.1.2%2C-FailoverTransport-and-Firewall-tp22001614p22001614.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
