[ https://issues.apache.org/jira/browse/ARTEMIS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce updated ARTEMIS-2644: ------------------------------------------ Fix Version/s: (was: 2.12.0) > Include client id into non durable subscriber queue name > -------------------------------------------------------- > > Key: ARTEMIS-2644 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2644 > Project: ActiveMQ Artemis > Issue Type: Improvement > Reporter: Domenico Bruscino > Priority: Major > Time Spent: 7h 50m > Remaining Estimate: 0h > > In many cases, we have users who can start up a java web start based user > interface, to receive notifications about events that may require manual > intervention. > For these, we typically use non-durable, non shared subscriptions. > These are identified in the broker only with a computed UID, ie a non durable > subscriber queue name: 4bd56221-3920-47e9-b5c1-f12015174d4d > Sometimes, these consumers can stop consuming, possibly through the user not > exiting cleanly, or perhaps with the virtualised desktop environment pausing > the UI. > We can look to killl these connections / queues from the broker side, but > since there is no hostname / application / user visible in the queue name, it > makes it hard to identify impacted business users. > This is a request to allow consuming applications to provide their own string > as part of the queue name, to assist with troubleshooting. -- This message was sent by Atlassian Jira (v8.3.4#803005)