[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910332&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910332
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/24 13:40
Start Date: 18/Mar/24 13:40
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4856:
URL:
https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2003937354
I don't understand your interim solution? you're forcing the registration if
address =management address?
I think everything should be manageable. (I have been bitten by that before)
you may want to hidden certain address from the console, that could reappear
after a toggle is selected.
(maybe we hide internal addresses?)
functionally I think we should have a flag to hide certain control queues
only... (that I don't have a name for them yet).
MQTT and OpenWire protocol managers have a few... even those should be able
to reappear after a select toggle on the console.
Issue Time Tracking
-------------------
Worklog Id: (was: 910332)
Time Spent: 6h 20m (was: 6h 10m)
> 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: 6h 20m
> 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)
