[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837376#comment-17837376
]
Robbie Gemmell edited comment on ARTEMIS-1921 at 4/15/24 5:19 PM:
------------------------------------------------------------------
The attached code tries _both_ the ConnectionFactory method that is impl-detail
and not part of the API (though is in the vein of 'administratively configured'
values the spec does speak to), as well as the Connection method that _is_ part
of the spec. The latter is portable.
was (Author: gemmellr):
The attached code tries _both_ the ConnectionFactory method that is impl-detail
and not part of the APUI (though is in the vein of 'administratively
configured' values the spec does speak to), as well as the Connection method
that _is_ part of the spec. The latter is portable.
> 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)
