You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/03/14 18:30:06 UTC
[jira] [Closed] (ARTEMIS-2081) When config reload occurs with
deletion policy enabled, queues not created by broker xml are removed
[ https://issues.apache.org/jira/browse/ARTEMIS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic closed ARTEMIS-2081.
------------------------------------
> When config reload occurs with deletion policy enabled, queues not created by broker xml are removed
> ----------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2081
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2081
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Major
> Fix For: 2.7.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> This is related to feature https://issues.apache.org/jira/browse/ARTEMIS-1235
> listConfiguredQueues was meant to return queues which are managed by broker xml, the intent is where a queue was created by a client (e.g. you configure durable queues, but allow clients to make non-durable queues still) on reload where the address exists, but the queue is not present, it would only remove queues that are being managed by broker.xml
> unfortunately this is not returning only queues that are created/managed by broker.xml, meaning on broker reload and the address is present, queues created by clients get un-expectedly removed.
> We need to track/mark queues explicitly that are created by configuration (broker.xml) and update the filter to use this new flag, to ensure only those are touched.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)