[
https://issues.apache.org/jira/browse/ARTEMIS-2787?focusedWorklogId=441863&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-441863
]
ASF GitHub Bot logged work on ARTEMIS-2787:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/20 15:03
Start Date: 05/Jun/20 15:03
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3169:
URL: https://github.com/apache/activemq-artemis/pull/3169#issuecomment-639551334
@michaelpearce-gain just one thing I'm wondering...
we have the hability to store pause / start on Queues.
wouldn't make sense to do the same? perhaps reuse the same record checking
if there's more bytes at the end?
----------------------------------------------------------------
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: 441863)
Time Spent: 4h (was: 3h 50m)
> 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: 4h
> 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)
