[
https://issues.apache.org/jira/browse/ARTEMIS-4924?focusedWorklogId=982840&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-982840
]
ASF GitHub Bot logged work on ARTEMIS-4924:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Sep/25 19:03
Start Date: 11/Sep/25 19:03
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #5921:
URL:
https://github.com/apache/activemq-artemis/pull/5921#issuecomment-3282280383
In my opinion the question of which DLA to use isn't significant. The main
thing is that we allow the bridge to function properly (i.e. by removing the
offending message) and put the message _somewhere_ rather than just drop it. By
default, this will be in the catch-all `DLQ`.
Issue Time Tracking
-------------------
Worklog Id: (was: 982840)
Time Spent: 3h (was: 2h 50m)
> Proper handling of 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
> Remaining Estimate: 0h
>
> Currently, if a poison message missing queue information ends up in the SF
> queue, the broker logs an error, like:
> AMQ222110: no queue IDs defined...
> but 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
