Return-Path: 
 <dev-return-24846-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: (qmail 30015 invoked from network); 6 Aug 2009 07:19:58 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 6 Aug 2009 07:19:58 -0000
Received: (qmail 92808 invoked by uid 500); 6 Aug 2009 07:20:05 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 92728 invoked by uid 500); 6 Aug 2009 07:20:04 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 92720 invoked by uid 99); 6 Aug 2009 07:20:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 07:20:04 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of mreutegg@day.com designates
 207.126.148.182 as permitted sender)
Received: from [207.126.148.182] (HELO eu3sys201aog002.obsmtp.com)
 (207.126.148.182)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 06 Aug 2009 07:19:53 +0000
Received: from source ([209.85.218.215]) by eu3sys201aob002.postini.com
 ([207.126.154.11]) with SMTP
	ID DSNKSnqEA98BbrC5V3GZSr9Q3W81o1lIb7gI@postini.com;
 Thu, 06 Aug 2009 07:19:33 UTC
Received: by bwz11 with SMTP id 11so561252bwz.39
        for <dev@jackrabbit.apache.org>; Thu, 06 Aug 2009 00:19:31 -0700 (PDT)
MIME-Version: 1.0
Sender: mreutegg@day.com
Received: by 10.223.123.210 with SMTP id q18mr3828439far.60.1249543170952;
	Thu, 06 Aug 2009 00:19:30 -0700 (PDT)
In-Reply-To: <24826284.post@talk.nabble.com>
References: <24823548.post@talk.nabble.com>
	 <a781e7950908050310q60756489x9461d84d84e09f66@mail.gmail.com>
	 <24824235.post@talk.nabble.com> <24824270.post@talk.nabble.com>
	 <a781e7950908050438o4d3aeadfv7c19dcd221f194f3@mail.gmail.com>
	 <24826284.post@talk.nabble.com>
Date: Thu, 6 Aug 2009 09:19:30 +0200
X-Google-Sender-Auth: 43d6d436bb048430
Message-ID: <a781e7950908060019n6297bdfcv99b402ac6eb18a7@mail.gmail.com>
Subject: Re: How to do Indexing and Extraction in Background threads
From: Marcel Reutegger <marcel.reutegger@gmx.net>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

the extractor timeout is set to high:

<param name=3D"extractorTimeout" value=3D"100000"/>

your current configuration will only defer text extraction into the
background when the extraction time is more than 100'000ms

you should rather use the default value (remove the parameter from the
configuration), which is 100ms.

please also make sure you apply the configuration changes to
workspace.xml and not just the repository.xml.

regards
 marcel

On Wed, Aug 5, 2009 at 14:46, Ajai<ajaiking@gmail.com> wrote:
>
> We are using 1.5
>
> Thanks
> Ajai
>
> Marcel Reutegger wrote:
>>
>> that looks OK to me. what version of jackrabbit are you using?
>>
>> regards
>> =A0marcel
>>
>> On Wed, Aug 5, 2009 at 12:18, Ajai<ajaiking@gmail.com> wrote:
>>>
>>> Also attaching the configuration as a text file
>>> http://www.nabble.com/file/p24824270/config.txt config.txt
>>>
>>>
>>>
>>> Ajai wrote:
>>>>
>>>> Thanks marcel for the response.
>>>> Please find below the configuration:
>>>>
>>>> <SearchIndex
>>>> class=3D"org.apache.jackrabbit.core.query.lucene.SearchIndex">
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =A0 </SearchIndex>
>>>>
>>>> Kindly let us know your thoughts
>>>>
>>>> Thanks,
>>>> Ajai G
>>>>
>>>>
>>>>
>>>> Marcel Reutegger wrote:
>>>>>
>>>>> can you please send the configuration again in plain text. the
>>>>> configuration didn't make it through.
>>>>>
>>>>> but in any case, you can set the parameter extractorPoolSize to the
>>>>> number of background threads that you want to give the text extractio=
n
>>>>> process. see also: http://wiki.apache.org/jackrabbit/Search
>>>>>
>>>>> regards
>>>>> =A0marcel
>>>>>
>>>>> On Wed, Aug 5, 2009 at 11:22, Ajai<ajaiking@gmail.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Whenever we add a document to the repository, the indexing and
>>>>>> extraction
>>>>>> seems to happen in the same thread. Due to this, the addition takes
>>>>>> around 8
>>>>>> secs for a 2.5 MB document.
>>>>>>
>>>>>> We would like to make this extraction and indexing to be done on a
>>>>>> background thread.
>>>>>>
>>>>>> I have the following configuration for searchIndex in the
>>>>>> repository.xml
>>>>>>
>>>>>> <SearchIndex
>>>>>>
>>>>>> =A0class=3D"org.apache.jackrabbit.core.query.lucene.SearchIndex">
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</SearchIndex>
>>>>>>
>>>>>> Please let us know if any configuraion changes needs to be made.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Ajai G
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/How-to-do-Indexing-and-Extraction-in-Backgroun=
d-threads-tp24823548p24823548.html
>>>>>> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/How-to-do-Indexing-and-Extraction-in-Background-t=
hreads-tp24823548p24824270.html
>>> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/How-to-do-Indexing-an=
d-Extraction-in-Background-threads-tp24823548p24826284.html
> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>
>