[jira] [Commented] (ARTEMIS-3372) Openwire - deleting a queue leaves consumers in limbo

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376000#comment-17376000 ] 

ASF subversion and git services commented on ARTEMIS-3372:
----------------------------------------------------------

Commit 7fc312ab5d5fed3decc25e197fcdc89fbcd2b019 in activemq-artemis's branch refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7fc312a ]

ARTEMIS-3372 - disconnect consumers on queue deletion event


> 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: 40m
>  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)