[
https://issues.apache.org/jira/browse/ARTEMIS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054196#comment-17054196
]
Michael Andre Pearce commented on ARTEMIS-2644:
-----------------------------------------------
As discussed in PRs, if a user wished to control queue name with JMS 2.0 for
non durable's they can make a shared non durable subscription, making a unique
subscription name per client.
Changing default naming of objects, would be impactful to all users, so is a -1
change.
If additional meta data to identify what/whom created a queue this can be added
the Queue, as like the user was added the other year, e.g. clientid and remote
address could be added the queue impl and then exposed up via imx making it
available to any metrics system and within the console.
> 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)
