NO-JIRA Add a note about the `jms-client-id` session metadata to the docs

This commit is contained in:
Jan Šmucr 2021-02-11 10:48:43 +01:00 committed by Clebert Suconic
parent 078b2c076e
commit 5dc038b537
1 changed files with 13 additions and 0 deletions

View File

@ -159,6 +159,19 @@ end asynchronous systems which is not possible using the standard JMS API. For
more information on this advanced feature please see the section [Guarantees of
sends and commits](send-guarantees.md).
###Identifying your session for management and debugging
Assigning IDs to your core sessions can help you with monitoring and debugging the cluster using the [management console](management-console.md).
```java
ClientSession session;
// ...
session.addMetaData(ClientSession.JMS_SESSION_IDENTIFIER_PROPERTY, "jms-client-id");
session.addMetaData("jms-client-id", "my-session");
```
Such ID will then appear in the **Client ID** column under the **Connections**, **Consumers** and **Producers** tabs.
If you are using the JMS API, the ``setClientID`` would give you the same effect.
### ClientConsumer
Clients use `ClientConsumer` instances to consume messages from a queue. Core