You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org> on 2012/02/29 00:50:55 UTC
[jira] [Commented] (AMQNET-371) NMSConnectionException does not
trigger failover recovery.
[ https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218715#comment-13218715 ]
Timothy Bish commented on AMQNET-371:
-------------------------------------
An exception response sent back from the broker is not considered a connection error in most cases as it usually indicates some critical error such as a security violation. The failover transport can't automatically fix those sorts of issues.
Also the change that you committed will not fix the connection or force reconnect logic but most likely put things in a bad state since it simply triggering partial interruption processing in the state tracker and forcing consumers to clear inflight messages but no reconnect is done.
> 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