You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Krzysztof Porebski (Jira)" <ji...@apache.org> on 2019/10/13 17:34:00 UTC
[jira] [Commented] (AMQNET-622) IConnection event listeners are not
invoke on reconnect
[ https://issues.apache.org/jira/browse/AMQNET-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950395#comment-16950395 ]
Krzysztof Porebski commented on AMQNET-622:
-------------------------------------------
I think we could replace part of INmsConnectionListener in favor to ConnectionInterruptedListeners and ConnectionResumedListeners but would need to make adjustments in nms api. Currently these events are parameterless. INmsConnectionListener based listeners provides additional information about broker uri to which connection was resumed or with which connection was lost.
> 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)