Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 28 Feb 2012 23:42:55 +0000 (UTC)
From: "Jim Gomes (Updated) (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1998939954.135.1330472575213.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <515395945.82.1330471975376.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQNET-371) NMSConnectionException does not
 trigger failover recovery.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes updated AMQNET-371:
-----------------------------

    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.  (was: When a failover protocol is used, it is expected that any network interruptions will be automatically recovered.  Currently, the broker can through an internal error and kick a client off, which then throws an NMSConnectionException.  This exception is not automatically handled by the failover protocol.)
    
> NMSConnectionException does not trigger failover recovery.
> ----------------------------------------------------------
>
>                 Key: AMQNET-371
>                 URL: https://issues.apache.org/jira/browse/AMQNET-371
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira