[ 
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910230&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910230
 ]

ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Mar/24 15:35
            Start Date: 16/Mar/24 15:35
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #4856:
URL: 
https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2002022693

   Hmmm... I think I figured out what's going on.
   
   When we implemented openWire advisors, we used an internal queue that was 
meant to be hidden.
   
   I'm not sure it will be sanitary to have open wire connections to a server 
and showing all the advisors on the admin console.
   
   
   It's different though from SNFs from Mirroring and Clustering.
   
   
   
   Perhaps we would need a separation from those, but I would rather add an 
attribute for hidden=true, rather than manageable. And have the code somewhat 
simpler.
   
   
   I will leave this PR open for now and not merge it before the release. 
Perhaps I will wait the new admin console merged before moving into this since 
we will probably want to show the advisors in certain cases.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 910230)
    Time Spent: 6h  (was: 5h 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: 6h
>  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)

Reply via email to