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

Posted to issues@activemq.apache.org by "Michael Andre Pearce (Jira)" <ji...@apache.org> on 2019/10/03 09:51:01 UTC

[jira] [Resolved] (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:all-tabpanel ]

Michael Andre Pearce resolved AMQNET-603.
-----------------------------------------
    Resolution: Fixed

> 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
>             Fix For: 1.8.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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.4#803005)