[
https://issues.apache.org/jira/browse/ARTEMIS-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355290#comment-17355290
]
ASF subversion and git services commented on ARTEMIS-3323:
----------------------------------------------------------
Commit 7ce9030e9f1235ce3040d2111780a8bbb62bf927 in activemq-artemis's branch
refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7ce9030 ]
ARTEMIS-3323 - ensure openwire message id is unique and consistent for the life
of a broker when converted from core
> Openwire messageId needs to be globally unique
> ----------------------------------------------
>
> Key: ARTEMIS-3323
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3323
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, OpenWire
> Affects Versions: 2.13.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The current openwire message id from a converted core message uses the
> connection id as the seed combined with the journal id. When a client id is
> specified on the core producer, the resulting message id may not be unique
> across brokers due to the alignment of journal ids.
> The result is potential duplicate suppression in error by an openwire client.
> This can happen for clusters or multiple standalone brokers.
> The fix is to combine the journal id with the broker node id, such that it is
> globally unique and static for the life of the broker, which is consistent
> for redelivery/failover reconnect
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
