Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 2796 invoked from network); 1 Mar 2007 14:17:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Mar 2007 14:17:13 -0000 Received: (qmail 83135 invoked by uid 500); 1 Mar 2007 14:17:20 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 83094 invoked by uid 500); 1 Mar 2007 14:17:20 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 83085 invoked by uid 99); 1 Mar 2007 14:17:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 06:17:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 06:17:10 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CB9C3714290 for ; Thu, 1 Mar 2007 06:16:50 -0800 (PST) Message-ID: <5974592.1172758610831.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 06:16:50 -0800 (PST) From: "Dominique Pfister (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Resolved: (JCR-773) Under heavy load, database journal may contain empty update records. In-Reply-To: <21775517.1172758490841.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister resolved JCR-773. ----------------------------------- Resolution: Fixed Problem identified: on some occasion, the temporary file's contents was not written to disk even after closing the FileOutputStream. Remedied by syncing on its file descriptor. Introduced a performance optimization, using in-memory records as long as size stays under a certain limit. Fixed in r513340. > Under heavy load, database journal may contain empty update records. > -------------------------------------------------------------------- > > Key: JCR-773 > URL: https://issues.apache.org/jira/browse/JCR-773 > Project: Jackrabbit > Issue Type: Bug > Components: core > Affects Versions: 1.2.2 > Reporter: Dominique Pfister > Assigned To: Dominique Pfister > > In a clustering scenario with a database journal, empty records may be produced. A passive node will then throw the following exception during its synchronization: > 28.02.2007 08:34:11 *ERROR* ClusterNode: Unexpected error while syncing of journal: null (ClusterNode.java, line 260) > java.lang.NullPointerException > at java.io.FilterInputStream.close(Unknown Source) > at org.apache.jackrabbit.core.journal.ReadRecord.close(ReadRecord.java:197) > at org.apache.jackrabbit.core.journal.DatabaseRecordIterator.close(DatabaseRecordIterator.java:148) > at org.apache.jackrabbit.core.journal.DatabaseRecordIterator.close(DatabaseRecordIterator.java:114) > at org.apache.jackrabbit.core.journal.AbstractJournal.doSync(AbstractJournal.java:196) > at org.apache.jackrabbit.core.journal.AbstractJournal.sync(AbstractJournal.java:165) > at org.apache.jackrabbit.core.journal.ClusterNode.sync(ClusterNode.java:283) > at org.apache.jackrabbit.core.journal.ClusterNode.run(ClusterNode.java:254) > at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.