Hi, Usually if there is a problem with the data store, the exception is different.
Could you post the complete stack trace please? Maybe the search index is out of sync with the repository. You could delete the search index and restart (in that case the index is re-built). If this doesn't help: The persistence managers support running a consistency check and fix. See: http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/persistence/bundle/BundleDbPersistenceManager.html <param name="consistencyCheck" value="true"/> <param name="consistencyFix" value="true"/> Regards, Thomas On Tue, May 12, 2009 at 2:37 PM, MatthiasR <[email protected]> wrote: > > I recently updated to Jackrabbit 1.5.5 because of Bug [JCR-2063] > (FileDataStore: garbage collection can delete files that are ...). > > Today after executing the garbage collecting I couldn't add new nodes > anymore. After looking into my code I found out that my subclass of > SimpleAccessManager retrives nodes by using the itemId > (session.getNodeById(itemId)). When executing the getNodeById method an > ItemNotFoundException is thrown. The exception comes from > org.apache.jackrrabbit.core.ItemManager.getItemData Line 284. > > I think the problem only occurs in 1.5.5. I suspect that the garbage > collecting has corrupted my repository (which is pretty bad :-((). > > Any ideas? > > Matthias Reischenbacher > -- > View this message in context: > http://www.nabble.com/ItemNotFoundException-after-Garbage-Collecting-FileDataStore-tp23501738p23501738.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
