atom feed9 messages in org.codehaus.btm.dev[btm-dev] [jira] Resolved: (BTM-44) T...
FromSent OnAttachments
Dennis Brakhane (JIRA)Mar 20, 2009 5:35 pm 
Ludovic Orban (JIRA)Mar 20, 2009 6:07 pm 
Ludovic Orban (JIRA)Mar 20, 2009 6:07 pm 
Ludovic Orban (JIRA)Mar 20, 2009 6:25 pm 
Ludovic Orban (JIRA)Mar 22, 2009 5:02 am 
Ludovic Orban (JIRA)Mar 22, 2009 5:10 am 
Ludovic Orban (JIRA)Jun 17, 2009 2:20 pm 
Ludovic Orban (JIRA)Aug 29, 2009 12:27 pm 
Ludovic Orban (JIRA)Oct 28, 2009 8:40 am 
Subject:[btm-dev] [jira] Resolved: (BTM-44) TransactionLogRecord does not get updated when modified, leading to transaction log corruption
From:Ludovic Orban (JIRA) (ji@codehaus.org)
Date:Aug 29, 2009 12:27:20 pm
List:org.codehaus.btm.dev

[
http://jira.codehaus.org/browse/BTM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ludovic Orban resolved BTM-44.

------------------------------

Resolution: Fixed

reported as fixed by user + test added

TransactionLogRecord does not get updated when modified, leading to transaction
log corruption

----------------------------------------------------------------------------------------------

Key: BTM-44 URL: http://jira.codehaus.org/browse/BTM-44 Project: BTM Issue Type: Bug Affects Versions: 1.3.3 Reporter: Dennis Brakhane Assignee: Ludovic Orban Fix For: 1.3.3

(This was originally reported in BTM-43, but I'm convinced now that it is a
different bug, if possible, please move the comments from BTM-43 to this one;
I'll just continue from where I left off in BTM-43) I haven't written a test case yet, but I think I know what causes the
corruption. In DiskJournal:355, if some (but not all) uniqueNames in danglingRecord are
removed, the danglingRecord isn't updated correctly: neither the crc32 nor the
record length are recalculated, resulting in a corrupt log entry to be written. (BTW: is there a reason .size() == 0 is used instead of isEmpty()?)