activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQNET-371) NMSConnectionException does not trigger failover recovery.
Date Wed, 29 Feb 2012 00:46:05 GMT


Jim Gomes commented on AMQNET-371:

Thanks for the review, Tim.  I'll take a closer look into this.  This is meant to solve an
actual problem we are experiencing in production.  For some reason, every two to four hours,
the broker (AMQ 5.5.0) kicks the client off with a connection exception error.  This flies
counter to what I want the failover protocol to do, and this change did actually fix the problem.
 It was able to continue on uninterrupted without completely hosing my client application.
 Perhaps it simply hid the problem by not going into the other exception handling call stack
that would destroy the connection.

Suggestions on how to go about handling these bogus broker errors at a low enough level so
that it doesn't bubble all the way up to the client level?  My client is not capable of restoring
all of its connections, sessions and consumer/producers without being restarted, and that's
not an option.
> NMSConnectionException does not trigger failover recovery.
> ----------------------------------------------------------
>                 Key: AMQNET-371
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ, Stomp
>    Affects Versions: 1.5.3
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>              Labels: broker, error, exception, failover
>             Fix For: 1.5.4, 1.6.0
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message