[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837970#comment-17837970
]
Justin Bertram commented on ARTEMIS-1921:
-----------------------------------------
The client ID won't be available to the security manager, but it can be
available on the internal {{RemotingConnection}} which will be visible via JMX.
This is already the case for AMQP and OpenWire. The fix for this issue will do
this for Core.
> Setting client ID on core JMS should be reflected in broker RemotingConnection
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-1921
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1921
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.1
> Reporter: Johan Stenberg
> Priority: Major
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client
> over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in
> the Artemis JMS Client is not available on the broker via
> RemotingConnection#getClientID().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
