Return-Path: 
 <users-return-697-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org
Received: (qmail 10187 invoked from network); 28 Aug 2006 12:12:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 28 Aug 2006 12:12:01 -0000
Received: (qmail 40257 invoked by uid 500); 28 Aug 2006 12:12:00 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 40244 invoked by uid 500); 28 Aug 2006 12:11:59 -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 40235 invoked by uid 99); 28 Aug 2006 12:11:59 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 05:11:59 -0700
X-ASF-Spam-Status: No, hits=0.2 required=10.0
	tests=FROM_NO_LOWER
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [194.8.61.2] (HELO mailslot1.tirol.gv.at) (194.8.61.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 05:11:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: problems with re-indexing the workspace
Date: Mon, 28 Aug 2006 14:11:35 +0200
Message-ID: <F186AC080E44C146BBE4A33472CFA79FA6166C@mxs01.tirol.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: problems with re-indexing the workspace
Thread-Index: AcbKmD9Z5OLmmClASXadUq/aXlV+dQAAHpHw
From: =?iso-8859-1?Q?K=D6LL_Claus?= <C.KOELL@TIROL.GV.AT>
To: <users@jackrabbit.apache.org>
X-OriginalArrivalTime: 28 Aug 2006 12:11:36.0363 (UTC)
 FILETIME=[1BE8EFB0:01C6CA9B]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

hi jukka ..

in my case (as described in a other mail ... repository with 2 Million =
documents) i have these parameters for the lucene indexer ..
to re-index the workspace

<param name=3D"minMergeDocs" value=3D"1000"/>
<param name=3D"maxMergeDocs" value=3D"1000000"/>
<param name=3D"mergeFactor" value=3D"10"/>=20

so my opinion is that the merger should work
if there are 10 index folders with 1000 nodes into a single index folder =
with 1000*10 nodes
similarly when there are 10 index folders with each 1000*10 nodes and so =
on till we reach the maxMergeDocs size

if i re-index the repository it runs about 6-7 hours and then i get the =
outofmemory and about 700 index folders.
for me its not pursuable why there are so much index folders.
after the error occurs i restart again the repository without deleting =
the index folders and they get merged into about 40-90 folders

maybe there is a bug in the merger and he doesnt work right while the =
filter scans the documents on a re-index process
if i put some documents into the reposiory again the merger works great =
when i call the save Method on the session.

i dont know how i can get a usefully debug trace from the re-index =
process because after about 7 hours the log file is very large
if i enable the debug level on log4j

claus
-----Urspr=FCngliche Nachricht-----
Von: Jukka Zitting [mailto:jukka.zitting@gmail.com]=20
Gesendet: Montag, 28. August 2006 13:51
An: users@jackrabbit.apache.org
Betreff: Re: problems with re-indexing the workspace

Hi,

On 8/28/06, Christian Zanata <christian.zanata@wavegroup.it> wrote:
> [ERROR] 20060825 17:06:40
> (org.apache.jackrabbit.core.observation.ObservationManagerFactory) -
> Synchronous EventConsumer threw exception. java.lang.OutOfMemoryError
>
> This error seems happening when the repository tries to re-index the
> workspace, but we don't have more stack traces.
> [...]
> could anybody heps us to understand what's happening?

There are two likely causes for that; either Lucene is running out of
memory while merging the index segments, or one of the index filters
runs out of memory trying to parse one of the binary documents in the
repository. Without a complete stack trace it is difficult to
determine the exact cause of the problems.

You might want to try modifying the Lucene parameters in the
SearchIndex configuration. See the Lucene documentation for options
that affect memory usage.

BR,

Jukka Zitting

--=20
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development