coder999o opened a new issue, #6302: URL: https://github.com/apache/rocketmq-dashboard/issues/6302
## Description Client connection diagnostics join `[type, clientId, groupOrTopic, address]` with `|` to detect exact duplicate records, then split that key to build diagnostic evidence. A pipe inside a field is treated as a field boundary. ## Steps to reproduce On `rocketmq-studio` at `5e4c39b0`, call `analyzeClientConnections` with two otherwise identical Producer records: | Record | Client ID | Resource | Address | | --- | --- | --- | --- | | A | `client\|partition` | `orders` | `10.0.1.10:49152` | | B | `client` | `partition\|orders` | `10.0.1.10:49152` | The distinct records produce the same identity key and an `EXACT_DUPLICATE_CONNECTION` issue. Its evidence incorrectly reports `clientId=client`, `resource=partition`, and `address=orders`. A second case is two genuinely identical records with `clientId=client|partition` and `groupOrTopic=orders|events`: the duplicate count is correct, but its client, resource and address fields are truncated or shifted. ## Expected behavior Distinct identity tuples stay distinct. Actual duplicate records preserve the complete Client ID, resource and address in their evidence. ## Verification Two deterministic regressions reproduced both failures on the unmodified source. This was tested with the diagnostics function and frontend fixtures, without a live Broker. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
