[
https://issues.apache.org/jira/browse/ARTEMIS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378020#comment-17378020
]
ASF subversion and git services commented on ARTEMIS-3372:
----------------------------------------------------------
Commit 3961fd1cf2837a43fc245cddbbaf4a5f81a4f8f8 in activemq-artemis's branch
refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=3961fd1 ]
ARTEMIS-3372 - ensure test verification happens after expected failover event
such that expected message is not tracked as a duplicate
> 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)
