[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910151&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910151
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/24 16:59
Start Date: 15/Mar/24 16:59
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4856:
URL:
https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2000076630
@AntonRoskvist this is your PR. I simplified it by removing the isManaged..
I have been having issues myself when I was in phone calls with customers..
and I strongly believe we should keep everything manageable. The only intent
for the internal queue was about redistribution and load balancing...
Having those managed should always be preferable. and I have a strong
opinion about this since it bit myself in production. (Just a heads up in case
anyone wants to argue that :) )... (kind of half joking here, but It's true).
I want to have this merged before the release on monday.
Issue Time Tracking
-------------------
Worklog Id: (was: 910151)
Time Spent: 5.5h (was: 5h 20m)
> 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: 5.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)
