[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=983358&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-983358
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Sep/25 16:24
Start Date: 16/Sep/25 16:24
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #5921:
URL:
https://github.com/apache/activemq-artemis/pull/5921#issuecomment-3299501228
@gtully, for the use-case in this PR the message will only end up in the DLQ
if it *doesn't* have the routing headers which means your concern is moot.
In any event, the test-case already has a consumer which receives the
messages from the DLQ with no issue.
Issue Time Tracking
-------------------
Worklog Id: (was: 983358)
Time Spent: 3h 40m (was: 3.5h)
> 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 40m
> 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
