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 2016/11/29 11:35:58 UTC

[jira] [Resolved] (AMQ-6522) KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error

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

Gary Tully resolved AMQ-6522.
-----------------------------
    Resolution: Fixed

> KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error 
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-6522
>                 URL: https://issues.apache.org/jira/browse/AMQ-6522
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB, Message Store
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.0
>
>
> Using setCheckForCorruptJournalFiles=true, there is a sanity check of the journal at startup - skipping through each of the journal files validating batch record checksums and magic in an effort to detect corruption early and drop the relevant messages or error out.
> There is an error in the check logic that assumes a batch record must be < 32k which is not the case if a message is > 32k
> Tidy up this check and add some more detail to the error messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)