Return-Path: 
 <users-return-17232-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Received: (qmail 70965 invoked from network); 23 Mar 2011 10:59:30 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 23 Mar 2011 10:59:30 -0000
Received: (qmail 16137 invoked by uid 500); 23 Mar 2011 10:59:30 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 16109 invoked by uid 500); 23 Mar 2011 10:59:30 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:users@jackrabbit.apache.org>
List-Id: <users.jackrabbit.apache.org>
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Received: (qmail 16101 invoked by uid 99); 23 Mar 2011 10:59:29 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 10:59:29 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of olimination@gmail.com
 designates 209.85.220.170 as permitted sender)
Received: from [209.85.220.170] (HELO mail-vx0-f170.google.com)
 (209.85.220.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 10:59:23 +0000
Received: by vxb39 with SMTP id 39so12251862vxb.1
        for <users@jackrabbit.apache.org>;
 Wed, 23 Mar 2011 03:59:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=R5kEeW0L+kJzEpgNRgYdE/NVLPXAb+Whmy9jQURr1xw=;
        b=cfJrTQD1VCT+nj6VjmqLFBz+GAZ16XpMzlorA2sm2hz44/IgBB82gGckJWfXZnfi3e
         YUh6iIWwXLx4fumFvLT5GFeSheD9x+kwZs4t5d2rwkn9JhpTCDyMf2X18ySR+QKF7y0K
         JGdGEnAt1bXJ48P3UitlJWl56pukyHxDKe1QM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=TIOG8ls33bcy3dhWKJiqiCQewmVOWv6FbIrX3Ct9hFpdpNAgFUNwcRq2QQyWRSIn/h
         JSX/FrjWXOfnBCsxsCu0EPQnuTriQhq5c17pXK3kpo+nvy+f7MaEn617BKpYde9sat6Z
         zJlk0oO29VQXitqzZCQa723tPUEH3ozafg93Y=
MIME-Version: 1.0
Received: by 10.52.97.227 with SMTP id ed3mr961725vdb.295.1300877943018; Wed,
 23 Mar 2011 03:59:03 -0700 (PDT)
Received: by 10.220.195.131 with HTTP; Wed, 23 Mar 2011 03:59:02 -0700 (PDT)
Date: Wed, 23 Mar 2011 11:59:02 +0100
Message-ID: <AANLkTi==kwr-FJ5nEVu9M-4rCjMrj42w0SgDqhapYBiE@mail.gmail.com>
Subject: How can I call the check consistency function programmatically?
From: olimination <olimination@gmail.com>
To: users@jackrabbit.apache.org
Content-Type: multipart/alternative; boundary=20cf307abeedb094e2049f243f9d

--20cf307abeedb094e2049f243f9d
Content-Type: text/plain; charset=UTF-8

Hi,

is there a best practice way how to check the repository's consistency in
advance before I do a restart of the server?
Does exist such a function which returns me "true" or "false" depending on
the repository(search or workspace persistence manager index) consistency
status?

This information would be helpful because if the repository is somehow
corrupt and it has to do a consistency check this may take a long time
during the next startup.

I know that I can configure a forced check for the search index in the
workspace.xml like this:
<param name="enableConsistencyCheck" value="true"/>
<param name="forceConsistencyCheck" value="true"/>

But is it also possible to get somehow the information if the repository is
corrupt or not?


Thanks for help!

kind regards,
Oli

--20cf307abeedb094e2049f243f9d--