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/08/20 09:48:00 UTC
[jira] [Updated] (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 ]
Krzysztof Porebski updated AMQNET-603:
--------------------------------------
Summary: AmqpProvider shouldn't signal exception when connection is explicitly closed (was: AmqpProvider shouldn't throw exception when connection is explicitly closed)
> 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 throw 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)