[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838597#comment-17838597
]
Robbie Gemmell commented on ARTEMIS-1921:
-----------------------------------------
Yep, wasn't commenting on the change (hadn't looked yet) but just the earlier
reply around why it didnt work (but doing one or the other probably did
previously due to other oddness). Have looked at the new change now and looks
good.
> 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
> Assignee: Justin Bertram
> 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)
