[jira] Commented: (JCR-708) SearchManager might throw when handling cluster event

["Dominique Pfister (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464733 ] 

Dominique Pfister commented on JCR-708:
---------------------------------------

Error message looks as follows:

*ERROR* [main] SearchManager: Unable to index node XXX: does not exist (SearchManager.java, line 353)
*ERROR* [main] ObservationDispatcher: Synchronous EventConsumer threw exception. (ObservationDispatcher.java, line 203)
java.lang.NullPointerException
        at org.apache.jackrabbit.core.query.lucene.MultiIndex$AddNode.<init>(MultiIndex.java:1311)
        at org.apache.jackrabbit.core.query.lucene.MultiIndex.update(MultiIndex.java:319)
        at org.apache.jackrabbit.core.query.lucene.SearchIndex.updateNodes(SearchIndex.java:309)
        at org.apache.jackrabbit.core.SearchManager.onEvent(SearchManager.java:380)
        ...


> SearchManager might throw when handling cluster event
> -----------------------------------------------------
>
>                 Key: JCR-708
>                 URL: https://issues.apache.org/jira/browse/JCR-708
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>            Priority: Minor
>
> When handling events that are generated from another node in the cluster, the SearchManager might try to index an index that does no longer exist. This results in an error message or even a NPE. The scenario looks as follows (A and B are nodes in a repository cluster)
> 1: A adds node N
> 2: A saves changes
> 3: A removes node N
> 4: A saves changes
> Upon receiving the event of a newly created node, B starts indexing node N. If this process hasn't been concluded before step 3 above, it will throw.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira