[
https://issues.apache.org/jira/browse/ARTEMIS-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426174#comment-17426174
]
ASF subversion and git services commented on ARTEMIS-3313:
----------------------------------------------------------
Commit c3d93f5590b97ab31a4a46fd324b01eb4548940c in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c3d93f5 ]
ARTEMIS-3313 routing-type conflict during import/export
> DLA messages disappear 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
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> DLA messages sometimes disappear 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
> 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)
