[
https://issues.apache.org/jira/browse/ARTEMIS-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reopened ARTEMIS-4183:
-------------------------------------
> Broker diagram is not properly updated when new nodes become available
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-4183
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4183
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.28.0
> Reporter: Erwin Dondorp
> Priority: Minor
> Attachments: image-2023-02-26-16-36-25-761.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Using an auto discovery cluster.
> When the number of nodes is reduced, the broker diagram is properly updated
> when the Refresh button is used.
> When the number of nodes is enlarged, the broker diagram is _not_ properly
> updated when the Refresh button is used. The new nodes are visible, but their
> cluster-connections are not shown. The diagram can easily be fixed by using
> the browser refresh button instead, or by temporarily switching tabs within
> the Artemis console.
> The following diagram shows the effect:
> !image-2023-02-26-16-36-25-761.png!
> left image: initial situation with 5 nodes
> middle image: 3 nodes are added, and after Refresh button is used
> right image: after page refresh
> -I know the JS code from the Console fairly well. I suspect a synchronisation
> error between the variables {{relations}} and {{{}hiddenRelations{}}}. I'll
> investigate and try to add a PR.-
> A PR is added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
