You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2024/04/15 18:01:00 UTC

[jira] [Updated] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection

     [ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-1921:
------------------------------------
    Summary: Setting client ID on core JMS should be reflected in broker RemotingConnection  (was: Setting clientID in artemis-jms-client has no effect)

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