[
https://issues.apache.org/jira/browse/ARTEMIS-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021934#comment-18021934
]
ASF subversion and git services commented on ARTEMIS-4924:
----------------------------------------------------------
Commit c8d7f8acf57ba7f1cc3cef2b80905e347f2f03c0 in activemq-artemis's branch
refs/heads/main from Howard Gao
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c8d7f8acf5 ]
ARTEMIS-4924 handle invalid messages in SNF queue
- Send invalid messages in SNF queue to DLA
- Add documentation for proper store-and-forward queue usage
> 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 50m
> 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
