[ https://issues.apache.org/jira/browse/ARTEMIS-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354455#comment-17354455 ]
Anton Roskvist commented on ARTEMIS-3313: ----------------------------------------- Hi, I got some more time to look into this issue and I think I have found the underlying problem... The original messages on their respective "auto-created" DLA are located on MUTICAST queues but retain their old _AMQ_ROUTING_TYPE saying they are ANYCAST messages (which is correct for their original queue). This works well for their current journal, but when exporting and importing said messages to a new journal they cannot get routed properly since the DLA address only has MULTICAST queues. (don't know why they get discarded instead of ending up on a new DLA though) I have been able to verify this by changing _AMQ_ROUTING_TYPE from 1 to 0 in the exported data-file. After that the messages can be imported and even "retried" successfully, meaning they end up on their original ANYCAST queue. They still have the _AMQ_ROUTING_TYPE set to the incorrect value though, so I don't know if that can cause any additional issues though. > DLQ messages disaperaring when running retry or 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 > > DLQ messages disapear when running retry or 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 > retry or 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. > It usually does not happen and I have yet to be able to reproduce it, but > reusing the message journal from backups give the same results every time. -- This message was sent by Atlassian Jira (v8.3.4#803005)