[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=982903&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-982903
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Sep/25 09:31
Start Date: 12/Sep/25 09:31
Worklog Time Spent: 10m
Work Description: gtully commented on PR #5921:
URL:
https://github.com/apache/activemq-artemis/pull/5921#issuecomment-3284518462
My only question, if a message ends up on the SNF DLQ or on the default DLQ,
is it now usable from there?
Do we need to strip the message of the SNF routing context?
Ideally a user would be able to resend from the console with minimal effort.
See if in the test you can easily get the message from the DLQ routed to a
local consumer of that address for example. My guess is that the snf routing
info in the message headers will get in the way unless we whack it.
Issue Time Tracking
-------------------
Worklog Id: (was: 982903)
Time Spent: 3h 20m (was: 3h 10m)
> Handle invalid messages in SNF queues
> -------------------------------------
>
> Key: ARTEMIS-4924
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4924
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.35.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Currently, if a poison message missing queue information ends up in the SF
> queue, the broker logs an error, like:
> {noformat}
> AMQ222110: no queue IDs defined...{noformat}
> However, the message remains in the queue with the result that the bridge
> continuously reconnects, encounters the failure, then evicts the bridge
> consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
