[ 
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837387#comment-17837387
 ] 

Robbie Gemmell commented on ARTEMIS-1921:
-----------------------------------------

I wasn't really getting into whether the current implementation is actually 
able to do what was expected, just noting the attached application code did 
also do something that is portable, which your reply didnt seem to cover by 
concentrating only on the other bit that isnt.

Reading again, it also seems like you were suggesting it only works for Qpid 
JMS due to setting it on the ConnectionFactory, but I dont believe that is the 
case. If a ClientID wasnt set on the ConnectionFactory 'administratively' (i.e 
via impl-detail setter or its URI options) then the client will actually create 
the TCP connection and authenticate, but defer establishing the bare AMQP 
connection (which carries the ClientID as its container-id) until such time a 
Connection method is called,  like setClientID first if you want to set the 
ClientID (and it hasnt been set 'administratively' already), or any other 
method if you don't want to (and havent already) set it . The client can be 
configured not to defer the bare AMQP connection like this, if you know you 
wont set a clientID and also e.g want to take a while before using the 
Connection.

> 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)

Reply via email to