[AMQNET-371] NMSConnectionException does not trigger failover recovery.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.3
• Fix Version/s: 1.5.4, 1.6.0
• Component/s: ActiveMQ, Stomp
• Labels: broker error exception failover
• Assignee: Jim Gomes
• Reporter: Jim Gomes
• Created: 28/Feb/12 23:32
• Updated: 02/May/13 02:29
• Resolved: 09/Mar/12 01:10

Description

When a failover protocol is used, it is expected that any network interruptions will be automatically recovered. Currently, an internal broker error send an error message to a client and kick it off. The client then throws an NMSConnectionException. This exception is not automatically handled by the failover protocol, and the client application is then forced to completely destroy and rebuild all connections, sessions, consumers and producers, if that's even possible without restarting.

Issue Links

• depends upon: AMQNET-372 ActiveMQ AdvisoryConsumer not properly initializing its Ack message.
• is duplicated by: AMQNET-374 Temp queues hanging after a while