[
https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950779#comment-16950779
]
Krzysztof Porebski edited comment on AMQNET-622 at 10/15/19 5:49 AM:
---------------------------------------------------------------------
[~michael.andre.pearce] As far as I know, there is no direct equiv of this in
jms api, thus I think it might be worth to consider this change.
I wouldn't worry about breaking these implementation you mentioned. We won't
break them automatically. They will have to explicitly reference the new
version of the api. As they are pretty dead it won't happen until somebody
decide to resurrect them. If he/she does, he/she will be in the position to
make necessary adjustments anyway.
was (Author: havret):
[~michael.andre.pearce] As far as I know, there is no direct equiv of this in
jms api, thus I think it might be worth to consider this change.
> 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)
