You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Chris Morgan (Jira)" <ji...@apache.org> on 2019/08/28 16:36:00 UTC

[jira] [Commented] (AMQNET-603) AmqpProvider shouldn't signal exception when connection is explicitly closed

    [ https://issues.apache.org/jira/browse/AMQNET-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917905#comment-16917905 ] 

Chris Morgan commented on AMQNET-603:
-------------------------------------

This might be as simple as checking the Error parameter for the amqpnetlite closed callback. To my knowledge at the connection the error parameter for the closed callback is null when an explicit amqpnetlite connection is closed without error.

> AmqpProvider shouldn't signal exception when connection is explicitly closed
> ----------------------------------------------------------------------------
>
>                 Key: AMQNET-603
>                 URL: https://issues.apache.org/jira/browse/AMQNET-603
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: AMQP, NMS
>    Affects Versions: 1.8.0
>            Reporter: Krzysztof Porebski
>            Priority: Major
>
> AmqpProvider shouldn't signal exception when connection is explicitly closed. It may lead to deadlocks when provider is used with Spring SimpleMessageListenerContainer.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)