[AMQNET-211] ConnectionInterruptedListener doesnt raise the event when broker network dies in failover mode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.2.0
• Component/s: ActiveMQ, NMS

Environment

ActiveMQ 5.3 stable release. tested also with ActiveMQ 5.4 Nightly build
Apache.NMS 1.2.0.1778
Apache.NMS.ActiveMQ.dll 1.2.0.1778

• Assignee: Jim Gomes
• Reporter: Sebastien Rodriguez
• Created: 23/Nov/09 12:16
• Updated: 07/Jan/11 03:25
• Resolved: 15/Jan/10 20:33

Description

The problem comes when I set up the following configuration:
Network of brokers (2 brokers, A and B) in failover mode
Client written in C# using the Apache.NMS.ActiveMQ client, configured in failover mode. (machine C)

When stopping manually the service in one computer(A for eg), the switch is done without any problems. C uses B to send the data. The admin console shows he has one consumer.
Turning the service on and doing the same step in the other computer works great too (the client failovers to the recovered broker again without any problems: C is connected to A now)
Unplugging the network cable in A does not cause C to switch to B again. Looking at the admin console there are no consumers connected to B.

Looking the logs of B:
jvm 1 | WARN | Could not start network bridge between: vm://10.216.1.66 and: tcp://10.216.1.101:61616 due to: java.net.ConnectException: Connection timed out: connect

This should have raised a ConnectionInterruptedListener event. Logs shoes nothing such happens

Issue Links

• depends upon: AMQNET-212 Add an Inactivity Monitor to the Transports layer to timeout broken connections