Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
2.11.3
-
None
-
None
Description
Using Jackrabbit 2.x, I am experiencing an issue that is similar if not identical to the JCR-773, which was "remedied" a long time. The stack trace of an exception looks like this:
java.lang.NullPointerException: null at java.io.FilterInputStream.close(FilterInputStream.java:181) at org.apache.jackrabbit.core.journal.ReadRecord.close(ReadRecord.java:212) at org.apache.jackrabbit.core.journal.DatabaseRecordIterator.close(DatabaseRecordIterator.java:155) at org.apache.jackrabbit.core.journal.DatabaseRecordIterator.close(DatabaseRecordIterator.java:121) at org.apache.jackrabbit.core.journal.AbstractJournal.doSync(AbstractJournal.java:263) at org.apache.jackrabbit.core.journal.DatabaseJournal.doSync(DatabaseJournal.java:458) at org.apache.jackrabbit.core.journal.AbstractJournal.internalSync(AbstractJournal.java:222) at org.apache.jackrabbit.core.journal.AbstractJournal.sync(AbstractJournal.java:190) at org.apache.jackrabbit.core.cluster.ClusterNode.internalSync(ClusterNode.java:340) at org.apache.jackrabbit.core.cluster.ClusterNode.syncOnStartup(ClusterNode.java:365) at org.apache.jackrabbit.core.cluster.ClusterNode.start(ClusterNode.java:277) at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:344)
Unfortunately, I cannot determine the root cause of the problem yet, because it appears to be sporadic. However, when it happens, none of the cluster members can ever get back to normal.
Questions
As pointed out before, the JCR-773 is marked as fixed so I assume there should be no errors like the ones I see. Anyway, it would be great if I could get an answer to the following question:
- Is this a known problem and if so, how can it be mitigated/eliminated?
Attachments
Issue Links
- is related to
-
JCR-773 Under heavy load, database journal may contain empty update records.
- Closed