[
https://issues.apache.org/jira/browse/AMQNET-603?focusedWorklogId=304605&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-304605
]
ASF GitHub Bot logged work on AMQNET-603:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Aug/19 21:20
Start Date: 30/Aug/19 21:20
Worklog Time Spent: 10m
Work Description: Havret commented on pull request #24: AMQNET-603:
AmqpProvider shouldn't signal exception when connection is explicitly closed
URL: https://github.com/apache/activemq-nms-amqp/pull/24
AmqpProvider shouldn't signal exception when connection is explicitly
closed. It may lead to deadlocks when provider is used with Spring
SimpleMessageListenerContainer.
This PR addresses this issue.
@cjwmorgan-sol Could you please take a look at this? It is implemented
according to your suggestion.
----------------------------------------------------------------
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: 304605)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
