[ https://issues.apache.org/jira/browse/ARTEMIS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611183#comment-16611183 ]
ASF GitHub Bot commented on ARTEMIS-2081: ----------------------------------------- Github user michaelandrepearce commented on the issue: https://github.com/apache/activemq-artemis/pull/2300 Leave it on 2.7 im of the opinion hot fix branch should be only for mission critical fixes. > 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 > Priority: Major > > 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)