[
https://issues.apache.org/jira/browse/ARTEMIS-2644?focusedWorklogId=398844&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-398844
]
ASF GitHub Bot logged work on ARTEMIS-2644:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/20 01:45
Start Date: 06/Mar/20 01:45
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #3002:
ARTEMIS-2644 Include client id into non durable subscriber queue name
URL: https://github.com/apache/activemq-artemis/pull/3002#issuecomment-595555227
Guys this is a breaking change as no longer with use core naming enabled the
naming patterns match with amqp.
Also this merged very quickly for a non critical fix can we please ask for
giving others time to review in future.
Can either this revert this or ensure amqp is alinged when amqp core naming
is toggled
----------------------------------------------------------------
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: 398844)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
