[
https://issues.apache.org/jira/browse/AMQ-9769?focusedWorklogId=990095&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-990095
]
ASF GitHub Bot logged work on AMQ-9769:
---------------------------------------
Author: ASF GitHub Bot
Created on: 03/Nov/25 18:04
Start Date: 03/Nov/25 18:04
Worklog Time Spent: 10m
Work Description: thezbyg commented on PR #1493:
URL: https://github.com/apache/activemq/pull/1493#issuecomment-3481837419
Rebased.
Connection `clientId` issue could be fixed by saving current `clientId`
value when registering connection MBean. Like this:
https://github.com/thezbyg/activemq/commit/53d7e53366b88ceb00d6f5a08aad5bd83c618891
This would ensure that `clientId` returned by `connection.getClientId()`
could not change after MBean is registered and would always match
`connectionName` property value in connection MBean object name.
Issue Time Tracking
-------------------
Worklog Id: (was: 990095)
Time Spent: 1h 40m (was: 1.5h)
> Add name property to connector interface and MBean
> --------------------------------------------------
>
> Key: AMQ-9769
> URL: https://issues.apache.org/jira/browse/AMQ-9769
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Components: Broker, Web Console
> Reporter: Albertas Vyšniauskas
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 6.2.1
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> {color:#000000}{color:#000000}ConnectorViewMBean{color}{color} does not have
> a name property and the only way to get connector name from MBean is
> "connectorName" JMX value. This is bad because JMX values are escaped and
> this escaping is non-reversible, so it is impossible to get the original
> connector name.
> Web console could use this new name property to show original connector name
> instead of the one mangled by JMX escaping.
--
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
