You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/06/01 11:14:00 UTC

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

Gary Tully created ARTEMIS-3323:
-----------------------------------

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