Am 08.01.2007 um 18:06 schrieb Christian Sylvestre:
I am getting exceptions stating that some content nodes don't exist
anymore:
org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl
DocOrderNodeIteratorImpl.java(compare:197) 08.01.2007 17:28:20 Node
c15bb042-14d3-4c6a-972e-0373807a9702 does not exist anymore:
javax.jcr.ItemNotFoundException: c15bb042-14d3-4
I don't think this is a condition that can/should never arise. It is
similar to running a sql query and then stepping through the results
only to find out that someone has subsequently deleted one of the
rows that at the time of your query existed. I have often seen such
errors pop up in the log files from workflow related timer based
actions.
I deleted the
\webapps\magnoliaAuthor\repositories\magnolia\workspaces\default\index
folder expecting that the index would be rebuilt.
To the best of my knowledge, this action eliminated the index for
your default workspace, which thankfully is probably both empty and
unused. I don't think that is a good idea to delete files out from
under lucene. As far as I know the index is updated as you add or
remove nodes from jackrabbit. I suspect it would therefore only be
rebuilt if you loaded a previous dump of your repository.
However I am still getting
the same exceptions. Any idea on what could be causing that problem
and on
how to avoid/fix it.
I get these errors every now and then, do nothing to fix them, and
eventually they go away again.
FYI I am using 3.0.1 with MySQL as persistence manager (using the
com.iorgagroup.jackrabbit.core.state.db.DataSourcePersistenceManager).
Thanks,
christian sylvestre
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
