[JCR-773] Under heavy load, database journal may contain empty update records.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1, 1.2.2, 1.2.3
• Fix Version/s: 1.3
• Component/s: jackrabbit-core
• Assignee: Dominique Pfister
• Reporter: Dominique Pfister
• Created: 01/Mar/07 14:13
• Updated: 20/May/16 22:48
• Resolved: 01/Mar/07 14:15

Description

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)

Issue Links

• relates to: JCR-3981 Null pointer exception on journal synchronization