You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/07/19 11:19:52 UTC

[jira] Resolved: (AMQ-2832) Possible replay of old messages post index recovery from journal - data files containing acks reclaimed/cleaned up in error

     [ https://issues.apache.org/activemq/browse/AMQ-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2832.
-----------------------------

    Resolution: Fixed

resolved in  r964804 KahaDB store and  r964866 AMQ store

Data files containing only acks for messages in referenced data files are now excluded from cleanup till the dependent message file is eligible for cleanup.

> Possible replay of old messages post index recovery from journal - data files containing acks reclaimed/cleaned up in error
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2832
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2832
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.2
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> With long lived messages and outstanding acks, ack distribution can be sparse across data files. If a data file is in use (still has unreferenced messages, the data files containing acks for all those messages also need to be maintained to ensure a replay of the journal replays the corresponding acks. Currently it is possible that data files with no unreferenced messages but with acks pertinent to an in use data file can get deleted. The result is duplicate or relay of old messages after journal recovery (following a crash/restart)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.