[
https://issues.apache.org/jira/browse/ARTEMIS-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033323#comment-18033323
]
ASF subversion and git services commented on ARTEMIS-5717:
----------------------------------------------------------
Commit 6d5cda320ad428a04bf7eb304f006532212381cf in activemq-artemis's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6d5cda320a ]
ARTEMIS-5717 Fix for lost messages from conflict of message routing types
When a message carries a routing type or a JMS destination type that conflicts
with the actual type of the address the message gets routed to the message can
be dropped with no matching routes which can lead to unexpected message loss.
This can happen when a message sent to a MULTICAST address is sent to a DLA
with an ANYCAST address type and then is sent to a DLA on a different broker
via a bridge of via a federation queue receiver link as one simple example.
> BrokerConnection Receiver would lose messages on routing type mismatch
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-5717
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5717
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Timothy A. Bish
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.44.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
--
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
