[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864220#comment-17864220
]
Justin Bertram commented on ARTEMIS-1921:
-----------------------------------------
[~bummer], I can't find a reference to the aforementioned code in the
documentation. Can you clarify what needs to be updated?
Also, the change here should be backwards compatible. Have you tested and
confirmed that if you set the client ID via the meta-data then it is not
visible in the console?
> 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
> Fix For: 2.34.0
>
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
> Time Spent: 20m
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
