[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=896049&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-896049
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Dec/23 10:55
Start Date: 18/Dec/23 10:55
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4670:
URL:
https://github.com/apache/activemq-artemis/pull/4670#issuecomment-1860136459
@jbertram This should address the issues you noted. In addition I also set
the `MQTT_SESSION_STORE` as "non manageable" since that is the destination
that caused a few of the previous tests to fail (it always gets created if the
broker starts with the mqtt-module enabled). Consequently, I reverted the
changes made to `queueMetrics.groovy` because they are no longer needed.
Issue Time Tracking
-------------------
Worklog Id: (was: 896049)
Time Spent: 5h (was: 4h 50m)
> 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: 5h
> 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)
