Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1140538779.1240411847962.JavaMail.jira@brutus>
Date: Wed, 22 Apr 2009 07:50:47 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2035) IndexingQueue not checked on initial
 index creation
In-Reply-To: <1632454161.1237372910635.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2035:
-------------------------------

    Fix Version/s:     (was: 1.6.0)
                   1.5.5

Merged to the 1.5 branch in revision 767551.

> IndexingQueue not checked on initial index creation
> ---------------------------------------------------
>
>                 Key: JCR-2035
>                 URL: https://issues.apache.org/jira/browse/JCR-2035
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.3, 1.4, 1.5.0
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5.5
>
>         Attachments: JCR-2035.patch
>
>
> With a default value of 100 for extractorBackLogSize and lots of text extractions that time out, the temp folder gets filled with extractor*.tmp files. This is because the IndexingQueue.getFinishedDocuments() is not called during the initial index creation. This is not an issue during regular operation because the method is called periodically from a timer thread.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.