[
https://issues.apache.org/jira/browse/ARTEMIS-2787?focusedWorklogId=441875&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-441875
]
ASF GitHub Bot logged work on ARTEMIS-2787:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/20 15:12
Start Date: 05/Jun/20 15:12
Worklog Time Spent: 10m
Work Description: michaelpearce-gain edited a comment on pull request
#3169:
URL: https://github.com/apache/activemq-artemis/pull/3169#issuecomment-639554539
so thats taken care of if you update config via jmx console, e.g. you would
call updateQueue passing in queueConfig json, and it has same behaviour as
updating via config.xml, it updates the queue config just like any other config
change on a queue, and is persited in the queue binding
https://github.com/apache/activemq-artemis/pull/3169/files#diff-1fae8ea746270e6f0b1f0c99a6148ab2
I wouldnt want queue settings persisted in two different journal place
places, like other queue config, should be all in the persisted queue binding.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 441875)
Time Spent: 5h 20m (was: 5h 10m)
> Allow a queue to be disabled, so that messages are not routed to it.
> --------------------------------------------------------------------
>
> Key: ARTEMIS-2787
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2787
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Michael Andre Pearce
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> There are a number of scenarios where it can be useful to disable a queue, so
> messages are not routed to it.
> 1) An issue that requires investigation but you wish to keep the consumers
> active, but do not wish to have message build up on the broker
>
> 2) you want to connect consumers to a address, but you do not wish the flow
> to start and wish to manage the enablement and disablement centrally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
