[
https://issues.apache.org/jira/browse/ARTEMIS-2081?focusedWorklogId=195829&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-195829
]
ASF GitHub Bot logged work on ARTEMIS-2081:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Feb/19 18:25
Start Date: 07/Feb/19 18:25
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2543:
ARTEMIS-2081 listConfiguredQueues returns only queues created by config
URL: https://github.com/apache/activemq-artemis/pull/2543#issuecomment-461541641
@jbertram ended up having to handle a number of conflicts when cherry
picking (so its not a true cherry pick), but think it's sorted.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 195829)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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)
