[ 
https://issues.apache.org/jira/browse/ARTEMIS-2420?focusedWorklogId=279063&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-279063
 ]

ASF GitHub Bot logged work on ARTEMIS-2420:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jul/19 14:58
            Start Date: 18/Jul/19 14:58
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on issue #2747: ARTEMIS-2420 
Add DLA prefix configuration property, to allow dynamic DLA/DLQ creation
URL: https://github.com/apache/activemq-artemis/pull/2747#issuecomment-512852740
 
 
   This is being replaced by #2760 
   
   Please I would like your review, to make sure everything is there before I 
merge it.
   
   
   I will be running a full testsuite before merging it.
 
----------------------------------------------------------------
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: 279063)
            Time Spent: 3h  (was: 2h 50m)
    Remaining Estimate: 9h  (was: 9h 10m)

> 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: 3h
>  Remaining Estimate: 9h
>
> 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)

Reply via email to