[
https://issues.apache.org/jira/browse/ARTEMIS-2420?focusedWorklogId=279358&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-279358
]
ASF GitHub Bot logged work on ARTEMIS-2420:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jul/19 21:32
Start Date: 18/Jul/19 21:32
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #2760:
ARTEMIS-2420 Adding support for DLA/DLQ prefix for wildcard addresses
URL: https://github.com/apache/activemq-artemis/pull/2760#issuecomment-512996503
Idea around security and address creation restrictions, could that both the
address and queue settings are checked both for the new address/queue and the
dead letter, before it is created. Thus meaning that either both create
(because permission and settings allow) or both wouldnt. Thus avoiding the
situation of one being created without the other
----------------------------------------------------------------
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: 279358)
Time Spent: 7h 40m (was: 7.5h)
Remaining Estimate: 4h 20m (was: 4.5h)
> Reimplementation of AMQ5 dead letter strategy queuePrefix
> ---------------------------------------------------------
>
> Key: ARTEMIS-2420
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2420
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.9.0
> Reporter: Piotr Klimczak
> Priority: Major
> Original Estimate: 12h
> Time Spent: 7h 40m
> Remaining Estimate: 4h 20m
>
> ActiveMQ Classic supports DLQ prefixes for dynamically created destinations.
> This causes regression when switching from AMQ5 to AMQ Artemis, therefore it
> should be reimplemented.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
