You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Markus Joschko (JIRA)" <ji...@apache.org> on 2004/12/14 22:36:55 UTC
[jira] Created: (JCR-30) Exception in SearchManager
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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "Markus Joschko (JIRA)" <ji...@apache.org>.
[ http://nagoya.apache.org/jira/browse/JCR-30?page=comments#action_56701 ]
Markus Joschko commented on JCR-30:
-----------------------------------
Yup. I sometimes use crx to look at the repository. But at the time the exception occurs only the java program accessed the repository (crx/tomcat wasn't running at that moment).
> 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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "David Nuescheler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (JCR-30) Exception in SearchManager
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=history ]
Marcel Reutegger closed JCR-30:
-------------------------------
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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
[jira] Resolved: (JCR-30) Exception in SearchManager
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=history ]
Marcel Reutegger resolved JCR-30:
---------------------------------
Resolution: Invalid
All right then, I'll resolve this as invalid...
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=comments#action_57474 ]
Marcel Reutegger commented on JCR-30:
-------------------------------------
As mentioned by David, this might happen when another process is using the same workspace data or jackrabbit died with a jvm crash. In the latter case it is possible that lucene leaves a lock file 'write.lock' in the index directory of the workspace. Deleting that file might allow you to start jackrabbit again.
I haven't been able to reproduce the behaviour you described by calling the method Node.orderBefore(). However I don't know the exact call sequence you have in your code (what were you doing before and after that call?).
Markus: could you please check whether you can reproduce this issue and what exact code is needed to do this? Thanks
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "Markus Joschko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=comments#action_57483 ]
Markus Joschko commented on JCR-30:
-----------------------------------
Lucky me, still have the experimental code fragments around ;-)
The following method throws the IOException:
public void movePageUpSNS(String lowerID,String higherID)
throws Exception {
Session session = repository.login(new SimpleCredentials("cUser", "".toCharArray()), null);
Node lowerNode = session.getNodeByUUID(lowerID);
Node higherNode = session.getNodeByUUID(higherID);
if(lowerNode.getParent().equals(higherNode.getParent())) {
lowerNode.getParent().orderBefore(nameWithIndex(lowerNode),nameWithIndex(higherNode));
session.save(); //<-exception
return;
}
}
The nodes are versionable and the parameters of the method are the unique IDs given by jackrabbit.
As I mentioned I viewed the repositry with crx in between (different username even if I'm not sure if this feature is yet implemented). Anyway I still can use the repository, as long as I can live with this exception.
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=comments#action_57498 ]
Marcel Reutegger commented on JCR-30:
-------------------------------------
I still cannot reproduce the IOException with the code in your last comment on my checkout.
Please do the following:
- shutdown the repository instance
- check the workspaces/default/index directory for a write.lock file. if there is such a file delete it.
- start the repository instance and run your orderBefore code again.
If you still see the IOException there must be more code involved to reproduce this issue.
Thanks
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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
[jira] Commented: (JCR-30) Exception in SearchManager
Posted by "Markus Joschko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-30?page=comments#action_57499 ]
Markus Joschko commented on JCR-30:
-----------------------------------
Sorry. Think I misunderstand you. After removing the lock file I don't get the exception any longer.
That's working fine.
> Exception in SearchManager
> --------------------------
>
> Key: JCR-30
> URL: http://issues.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://issues.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