[
https://issues.apache.org/jira/browse/ARTEMIS-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879369#comment-17879369
]
Erwin Dondorp commented on ARTEMIS-4182:
----------------------------------------
[~jbertram]
your PR as a great step forward as it is now possible to identify the remote
nodes without having to lookup networking details.
would it be somehow possible to choose the implementation?
the implementation in your PR is {{server.getNodeID().toString()}}, which is
consistent with other connections.
an alternative would be {{server.getConfiguration().getName()}}, which is more
recognizable.
> fill client-id for cluster connections
> --------------------------------------
>
> Key: ARTEMIS-4182
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4182
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Broker
> Affects Versions: 2.28.0
> Reporter: Erwin Dondorp
> Priority: Major
> Attachments: image-2023-02-25-13-27-08-542.png, screenshot-2.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> when running Artemis in a cluster, the brokers have connections between them.
> these are easily identifiable in the list of connections because the "Users"
> field is filled in with the username that was specified in setting
> `cluster-user`.
> but it is unclear where each connection goes to.
> !image-2023-02-25-13-27-08-542.png!
>
> additional information:
> the field "Client ID" is filled in with the remote hostname when using
> broker-connection/amqp-connection.
> wish:
> (also) fill in field ClientID of the cluster connections.
> e.g. with the broker-name or from a new parameter `cluster-clientid`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
