[
https://issues.apache.org/jira/browse/JCR-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500947
]
Ian Boston commented on JCR-931:
--------------------------------
You might want to check what you transaction isolation is.
In MySQL if its REPEATABLE-READ the nodes added on other nodes will not be
updated on the current node until the current node does a commit.
if its READ-COMMITTED the underlying problem might go away.
I've been seeing simular problems that went away once the DB transaction
isolation was put right, some versions of MySQL come shipped with
REPEATABLE-READ on InnoDB (which you must use)
> cluster synchronization NPE
> ---------------------------
>
> Key: JCR-931
> URL: https://issues.apache.org/jira/browse/JCR-931
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Xiaohua Lu
> Fix For: 1.4
>
>
> we have a 4 machines setup and encountered the following NPE in one of the
> nodes. After restarting tomcat, the problem seems to go away. But it would be
> nice to find out why.
> java.lang.NullPointerException
> at
> org.apache.jackrabbit.core.query.lucene.NodeIndexer.createDoc(NodeInd
> exer.java:146)
> at
> org.apache.jackrabbit.core.query.lucene.SearchIndex.createDocument(Se
> archIndex.java:566)
> at
> org.apache.jackrabbit.core.query.lucene.SearchIndex$2.next(SearchInde
> x.java:368)
> at
> org.apache.jackrabbit.core.query.lucene.MultiIndex.update(MultiIndex.
> java:354)
> at
> org.apache.jackrabbit.core.query.lucene.SearchIndex.updateNodes(Searc
> hIndex.java:356)
> at
> org.apache.jackrabbit.core.SearchManager.onEvent(SearchManager.java:4
> 23)
> at
> org.apache.jackrabbit.core.observation.EventConsumer.consumeEvents(Ev
> entConsumer.java:231)
> at
> org.apache.jackrabbit.core.observation.ObservationDispatcher.dispatch
> Events(ObservationDispatcher.java:201)
> at
> org.apache.jackrabbit.core.observation.EventStateCollection.dispatch(
> EventStateCollection.java:424)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager.externalUpdat
> e(SharedItemStateManager.java:882)
> at
> org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.externalUpdat
> e(RepositoryImpl.java:1957)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.end(ClusterNode.java:8
> 34)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.consume(ClusterNode.ja
> va:929)
> at
> org.apache.jackrabbit.core.journal.AbstractJournal.doSync(AbstractJou
> rnal.java:191)
> at
> org.apache.jackrabbit.core.journal.AbstractJournal.sync(AbstractJourn
> al.java:166)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.sync(ClusterNode.java:
> 283)
> at
> org.apache.jackrabbit.core.cluster.ClusterNode.start(ClusterNode.java
> :229)
> at
> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:
> 308)
> at
> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:
> 584)
> at
> org.apache.jackrabbit.core.jndi.BindableRepository.createRepository(B
> indableRepository.java:174)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
