[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Reopened] (AMQNET-371) NMSConnectionException does not trigger failover recovery.
From:       "Timothy Bish (Reopened) (JIRA)" <jira+amqnet () apache ! org>
Date:       2012-02-28 23:52:55
Message-ID: 507782895.205.1330473175481.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

Timothy Bish reopened AMQNET-371:
---------------------------------


Changes aren't valid and not test cases were supplied.
                
> 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

        


[prev in list] [next in list] [prev in thread] [next in thread]