[
https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950721#comment-16950721
]
Michael Andre Pearce edited comment on AMQNET-622 at 10/14/19 5:43 AM:
-----------------------------------------------------------------------
-1 making changes to the api, NMS is meant to be an equiv of JMS. As well
please remember there are other existing implementations out the there, e.g.
openwire, stomp, tibco ems .... of the nms api.
Why not have two different extension types of the exceptions you throw
was (Author: michael.andre.pearce):
-1 making changes to the api, nms is meant to be an equiv of JMS.
Why not have two different extension types of the exceptions you throw
> IConnection event listeners are not invoke on reconnect
> -------------------------------------------------------
>
> Key: AMQNET-622
> URL: https://issues.apache.org/jira/browse/AMQNET-622
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: AMQP
> Reporter: Chris Morgan
> Priority: Major
>
> I found the Apache.NMS.AMQP.NMSConnection allows applications to add
> ConnectionInterruptedListeners and ConnectionResumedListeners however these
> event callbacks are never invoked even during failover/reconnect.
> The NMS AMQP provider does have a INmsConnectionListener to handle the
> interrupted and resumed connection events so its unclear whether
> ConnectionInterruptedListeners and ConnectionResumedListeners are not
> supported in favour for the INmsConnectionListener or if the
> ConnectionInterruptedListeners and ConnectionResumedListeners need to be
> invoked in addition to the INmsConnectionListener events.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
