You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/03/27 03:11:00 UTC

[jira] [Commented] (ARTEMIS-1769) Return JMS Session's ClientID via JMX

    [ https://issues.apache.org/jira/browse/ARTEMIS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414947#comment-16414947 ] 

Justin Bertram commented on ARTEMIS-1769:
-----------------------------------------

This patch can't be merged as-is. It needs some work. I'll elaborate tomorrow.

> Return JMS Session's ClientID via JMX
> -------------------------------------
>
>                 Key: ARTEMIS-1769
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1769
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.5.0
>            Reporter: Maxim Kalina
>            Priority: Minor
>              Labels: patch
>             Fix For: 2.5.1
>
>         Attachments: return_jms_session's_clientID_via_JMX_if_exists.patch
>
>
> As discussed in the mailing list, currently there is no possibility to get the JMS session's *clientID* via JMX.
>  
> I've attached the patch that extends the *ActiveMQServerControlImpl* and 
> *SessionView* classes to return the *clientID* if available.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)