Hi Marc,
ah, right, only the BundleDbPersistenceManagers come with those two parameters.
please note that the BundleFsPersistenceManager is not transactional and is not
a recommended persistence manager for a production system.
there's an errorHandling parameter, that you may try out. It handles cases where
binary properties are missing.
<param name="errorHandling" value="IGN_MISSING_BLOBS"/>
If that doesn't help, then you probably have to manually fix the bundle on the
file system. Unless someone else knows about a tool that can fix it for you.
regards
marcel
Marc Schriftman wrote:
Marcel,
Just to be clear - the consistencyCheck/consistencyFix functionality appears
to live in BundleDbPersistenceManager and I'm using
BundleFsPersistenceManager. I added those parameters to my workspace.xml
anyway, and restarted the repository, but there was no obvious change.
Regards,
Marc Schriftman
On Wed, Jun 11, 2008 at 8:10 AM, Marcel Reutegger <[EMAIL PROTECTED]>
wrote:
Hi Marc,
you need to set two parameters in your workspace.xml inside the
PersistenceManager tag:
<param name="consistencyCheck" value="true"/>
<param name="consistencyFix" value="true"/>
on startup, jackrabbit will run a consistency check and fix any
inconsistencies. this should allow the query handler to re-index the
workspace again.
regards
marcel
Marc Schriftman wrote:
Marcel -
I'm on 1.4.4 and I'm using
org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager.
I've a lot of data in my repository, and it scares me to think that I
can't
rebuild my indexes. What can I do to fix the inconsistency?
Thanks again for your help,
Marc Schriftman
