[ https://issues.apache.org/jira/browse/JCR-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472430#comment-15472430 ]
liang cheng commented on JCR-3981: ---------------------------------- one of our customer also hit this issue. It's really urgent for us > Null pointer exception on journal synchronization > ------------------------------------------------- > > Key: JCR-3981 > URL: https://issues.apache.org/jira/browse/JCR-3981 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core > Affects Versions: 2.11.3 > Reporter: Illia Khokholkov > > 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: > {noformat} > 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) > {noformat} > 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? -- This message was sent by Atlassian JIRA (v6.3.4#6332)