value of this cookie which contains a UUID to lookup the details of the profile. For example with the SSH console you can simply to: profile-view PROFILE_UUID import {useTracker} from "apache-unomi-tracker"; pageViewCount on the user’s profile. You can then reload then page and check with the profile-view PROFILE_UUID SSH command that the profile was updated with the new property and that it is incremented on each will be used instead. curl --location --request GET 'http://localhost:8181/cxs/profiles/PROFILE_UUID' \ --header 'Authorization: Basic a2FyYWY6a2FyYWY=' \ SHELL curl --location --request POST 'htt

supports durable and non-durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription temporary queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: ... ClientMessage message =

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

durable and non- durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting String , and its value should be unique. An easy way of generating a unique id is by generating a UUID. Here's an example of setting the property using the core API: And here's an example using the JMS

supports durable and non-durable subscriptions. The queue for a non-durable subscription is named with a UUID, but the queue used for a durable subscription is named according to the JMS "client ID" and "subscription queues are created by the broker using a UUID (i.e universally unique identifier) as the name for both the address and the queue. Because the name is a UUID it is impossible to create an address-setting  the string value provided will be converted internally into a 16 byte UUID, so it may not be immediately recognisable or human-readable, however it will ensure that all 'peers'