[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837379#comment-17837379 ]
Justin Bertram commented on ARTEMIS-1921: ----------------------------------------- The latter _is portable_ as you note. However, the fact that the client ID is set _after the connection is created_ means that the client ID will *not* be passed to the security manager which is the desired behavior here. > Setting clientID in artemis-jms-client has no effect > ---------------------------------------------------- > > 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 > > > 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)