[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=893851&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-893851
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Dec/23 19:03
Start Date: 04/Dec/23 19:03
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4670:
URL:
https://github.com/apache/activemq-artemis/pull/4670#issuecomment-1839285668
I went a different direction on this. You can see it on #4702. See the
updated description on
[ARTEMIS-4498](https://issues.apache.org/jira/browse/ARTEMIS-4498) for
additional details.
Issue Time Tracking
-------------------
Worklog Id: (was: 893851)
Time Spent: 2h 50m (was: 2h 40m)
> 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: 2h 50m
> 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)
