[jira] [Commented] (ARTEMIS-3323) Openwire messageId needs to be globally unique

["Gary Tully (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355016#comment-17355016 ] 

Gary Tully commented on ARTEMIS-3323:
-------------------------------------

ARTEMIS-2650 changed the id from uuid based, which was unique but not consistent to connection id based which was typically uuid and consistent but not when a user set the clientId on the connection factory.

> 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
>
>
> 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)