You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "David Nuescheler (JIRA)" <ji...@apache.org> on 2004/12/15 11:02:59 UTC

[jira] Commented: (JCR-30) Exception in SearchManager

     [ http://nagoya.apache.org/jira/browse/JCR-30?page=comments#action_56698 ]
     
David Nuescheler commented on JCR-30:
-------------------------------------

i got this exception a number of times before when i started a number
of repository instances on the same repository configuration. could that
be the case in your setup?

> Exception in SearchManager
> --------------------------
>
>          Key: JCR-30
>          URL: http://nagoya.apache.org/jira/browse/JCR-30
>      Project: Jackrabbit
>         Type: Bug
>  Environment: Rev 111526
>     Reporter: Markus Joschko
>     Priority: Minor

>
> After using Node.orderBefore(String,String) I did a session.save() and get the following exception:
> 2004-12-14 22:23:40,084 ERROR org.apache.jackrabbit.core.SearchManager - error indexing node.
> java.io.IOException: Lock obtain timed out
>  at org.apache.lucene.store.Lock.obtain(Lock.java:97)
>  at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:173)
>  at org.apache.jackrabbit.core.search.lucene.AbstractIndex.getIndexWriter(AbstractIndex.java:107)
>  at org.apache.jackrabbit.core.search.lucene.AbstractIndex.addDocument(AbstractIndex.java:81)
>  at org.apache.jackrabbit.core.search.lucene.SearchIndex.addDocument(SearchIndex.java:74)
>  at org.apache.jackrabbit.core.SearchManager.addNode(SearchManager.java:105)
>  at org.apache.jackrabbit.core.SearchManager.onEvent(SearchManager.java:252)
>  at org.apache.jackrabbit.core.observation.EventConsumer.consumeEvents(EventConsumer.java:195)
>  at org.apache.jackrabbit.core.observation.ObservationManagerFactory.dispatchEvents(ObservationManagerFactory.java:215)
>  at org.apache.jackrabbit.core.observation.EventStateCollection.dispatch(EventStateCollection.java:217)
>  at org.apache.jackrabbit.core.SessionImpl.dispatch(SessionImpl.java:310)
>  at org.apache.jackrabbit.core.state.tx.XASessionImpl.dispatch(XASessionImpl.java:418)
>  at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1249)
>  at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:633)
> However the new order of the nodes is saved, before that crash.
> I'm not sure if this crash is related to my environment, or if this is a bug.
> Not sure if it matters in this context: I didn't use locks in the moment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira