activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1221) Duplicated ID causes LargeMessage lost at backup
Date Thu, 29 Jun 2017 16:56:00 GMT

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

ASF GitHub Bot commented on ARTEMIS-1221:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1347


> Duplicated ID causes LargeMessage lost at backup
> ------------------------------------------------
>
>                 Key: ARTEMIS-1221
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1221
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.5, 2.1.0
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 1.5.6, 2.2.0
>
>
> When a large message is replicated to backup, a pendingID is generated when the large
message is finished. This pendingID is generated by a BatchingIDGenerator at backup.
> It is possible that a pendingID generated at backup may be a duplicate to an ID generated
at live server. 
> This can cause a problem when a large message with a messageID that is the same as another
largemessage's pendingID is replicated and stored in the backup's journal, and then a deleteRecord
for the pendingID is appended.
> If backup becomes live and loads the journal, it will drop the large message add record
because there is a deleteRecord of the same ID (even though it is a pendingID of another message).
As a result the expecting client will never get this large message.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message