[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864086#comment-17864086
]
Jan Šmucr commented on ARTEMIS-1921:
------------------------------------
I have a suspicion that this commit causes the client ID no longer being
visible in the management console if set as per documentation:
{code}
session.addMetaData(ClientSession.JMS_SESSION_IDENTIFIER_PROPERTY,
"jms-client-id")
session.addMetaData("jms-client-id", "my-session")
{code}
As this approach no longer works, how do I set the connection ID for my CORE
client so that it's 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
