[
https://issues.apache.org/jira/browse/AMQNET-603?focusedWorklogId=304646&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-304646
]
ASF GitHub Bot logged work on AMQNET-603:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Aug/19 22:29
Start Date: 30/Aug/19 22:29
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #24: AMQNET-603:
AmqpProvider shouldn't signal exception when connection is explicitly closed
URL: https://github.com/apache/activemq-nms-amqp/pull/24#issuecomment-526768484
@Havret @cjwmorgan-sol anything else outstanding apart from README to be
updated, before we try for a first cut release?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 304646)
Time Spent: 40m (was: 0.5h)
> 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
> 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.2#803003)
