[
https://issues.apache.org/jira/browse/ARTEMIS-3313?focusedWorklogId=611826&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-611826
]
ASF GitHub Bot logged work on ARTEMIS-3313:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jun/21 09:29
Start Date: 16/Jun/21 09:29
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on pull request #3621:
URL: https://github.com/apache/activemq-artemis/pull/3621#issuecomment-862204929
@jbertram Seems the retry was a simple fix, I added that now.
@brusdev Now also setting the original routingType when retrying messages
from DLA and HDR_ORIG_ROUTING_TYPE is set
--
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: 611826)
Time Spent: 1h (was: 50m)
> DLA messages disapear when running export/import
> ------------------------------------------------
>
> Key: ARTEMIS-3313
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3313
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.16.0, 2.17.0
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> DLQ messages disapear when running export/import
> This only seem to happen on dead letter queues where dead-letter resources
> are created automatically
> When running debug logging the following shows up for every message during
> import:
> DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl]
> Message CoreMessage[MESSAGE] is not going anywhere as it didn't have a
> binding on address:QUEUENAME
> All other queue information gets imported though, down to the dead letter
> filter. Just not the messages.
>
> This seems to be reproducible by simply:
> - configuring "auto-create-dead-letter-resources"
> - sending a message to an ANYCAST queue
> - sending that message to DLA
> - run the "export" tool
> - Get a fresh/empty journal
> - import the data export
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
