[ 
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=893882&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-893882
 ]

ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Dec/23 20:51
            Start Date: 04/Dec/23 20:51
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on PR #4670:
URL: 
https://github.com/apache/activemq-artemis/pull/4670#issuecomment-1839456056

   @AntonRoskvist, FWIW I think this was a good PR. I didn't want to ask you to 
make all the changes to implement what I eventually sent in #4702. However, now 
that I've sent it and it's all green I think you can close this one. Thanks!




Issue Time Tracking
-------------------

    Worklog Id:     (was: 893882)
    Time Spent: 3h 10m  (was: 3h)

> Enable management for internal addresses & queues
> -------------------------------------------------
>
>                 Key: ARTEMIS-4498
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4498
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Anton Roskvist
>            Priority: Major
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Originally "internal" addresses and queues weren't meant to be exposed via 
> management. However, due to a bug where the "internal" attribute of a queue 
> was not persisted properly such queues have been exposed to management for a 
> long time. This was fixed via ARTEMIS-4396, but users still want the ability 
> to manage internal queues because it is extremely helpful when trying to 
> troubleshoot issues. Therefore, this functionality should be configurable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to