[
https://issues.apache.org/jira/browse/ARTEMIS-4182?focusedWorklogId=933675&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-933675
]
ASF GitHub Bot logged work on ARTEMIS-4182:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Sep/24 21:34
Start Date: 06/Sep/24 21:34
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #5208:
URL:
https://github.com/apache/activemq-artemis/pull/5208#issuecomment-2334840956
@tabish121, thanks for the heads-up. I see what's happening now after much
head-scratching. I'll need to rework this PR so that the client ID is
configurable because having it always-on may not fit every use-case.
Issue Time Tracking
-------------------
Worklog Id: (was: 933675)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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
