[
https://issues.apache.org/jira/browse/AMQNET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219551#comment-13219551
]
Timothy Bish commented on AMQNET-371:
-------------------------------------
Can you capture in the NMS Client's log what the exception object is that the
broker is sending back, it should contain an error Message and the StackTrace
elements. That might help determine what is going on. Might have to enable
trace on the tcp Transport useLogging=true.
> 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
