[
https://issues.apache.org/jira/browse/ARTEMIS-3372?focusedWorklogId=619595&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-619595
]
ASF GitHub Bot logged work on ARTEMIS-3372:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Jul/21 20:16
Start Date: 06/Jul/21 20:16
Worklog Time Spent: 10m
Work Description: clebertsuconic merged pull request #3640:
URL: https://github.com/apache/activemq-artemis/pull/3640
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 619595)
Time Spent: 50m (was: 40m)
> Openwire - deleting a queue leaves consumers in limbo
> -----------------------------------------------------
>
> Key: ARTEMIS-3372
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3372
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> openwire consumers are in limbo if a queue is deleted by a management
> operation.
> with activemq5 - any message sent will recreate the queue and the consumers
> will resume.
> however with Artemis, the send it to an address, independent of the consumer
> queue. The send will continue to drop messages till the binding/queue is
> recreated.
> Any openwire consumer disconnect (typical on queue deletion) needs to be
> implemented as connection error/fail to force a possible client failover
> event and a recreation of the queue/binding.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
