[
https://issues.apache.org/jira/browse/ARTEMIS-2644?focusedWorklogId=399616&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-399616
]
ASF GitHub Bot logged work on ARTEMIS-2644:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/20 08:14
Start Date: 07/Mar/20 08:14
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #3006:
ARTEMIS-2644 Fix AMQP naming convention in compatibility mode with CORE
URL: https://github.com/apache/activemq-artemis/pull/3006#issuecomment-596060217
To be honest the more you look at this changing this logic everywhere is
lookingdangerous as breaking some bits possible. Also what occurs when someone
wants some other bit of data attached, we change it all again? Meah yucky
Is the issue that you just need to identify the creator of a queue? Instead
of changing the naming strategy why not have meta data on the queue itself, e.g
add client id, user and remote address onto the queue meta data?
We already have user on the queue, just add additional bits into the queue
and expose via jmx so available for metrics and console.
This also then would work even if clients not upgraded which with core youre
relying on.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 399616)
Time Spent: 5h (was: 4h 50m)
> 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
> Fix For: 2.12.0
>
> Time Spent: 5h
> 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)
