Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B44AF9C11 for ; Fri, 9 Mar 2012 01:12:25 +0000 (UTC) Received: (qmail 6360 invoked by uid 500); 9 Mar 2012 01:12:24 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 6158 invoked by uid 500); 9 Mar 2012 01:12:24 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 6134 invoked by uid 99); 9 Mar 2012 01:12:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2012 01:12:24 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2012 01:12:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id CC38F103F0 for ; Fri, 9 Mar 2012 01:11:59 +0000 (UTC) Date: Fri, 9 Mar 2012 01:11:59 +0000 (UTC) From: "Jim Gomes (Resolved) (JIRA)" To: dev@activemq.apache.org Message-ID: <698672863.41908.1331255519837.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <515395945.82.1330471975376.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (AMQNET-371) NMSConnectionException does not trigger failover recovery. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-371. ------------------------------ Resolution: Fixed > 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 > > Attachments: TQTest.zip > > 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