[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910348&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910348 ]
ASF GitHub Bot logged work on ARTEMIS-4498: ------------------------------------------- Author: ASF GitHub Bot Created on: 18/Mar/24 14:53 Start Date: 18/Mar/24 14:53 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2004134298 @AntonRoskvist I would rather delay this fix and do a proper fix in the next release. I'm looking to fix this before the next release, which may be a shorter release (timewise on when we are releasing it). Issue Time Tracking ------------------- Worklog Id: (was: 910348) Time Spent: 6h 40m (was: 6.5h) > 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 40m > 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)