Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1798135509.1259586440706.JavaMail.jira@brutus>
Date: Mon, 30 Nov 2009 13:07:20 +0000 (UTC)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2413) AlreadyClosedException on initial index
 creation
In-Reply-To: <829646143.1259574920630.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-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated JCR-2413:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

Applied patch in revision: 885411

> AlreadyClosedException on initial index creation
> ------------------------------------------------
>
>                 Key: JCR-2413
>                 URL: https://issues.apache.org/jira/browse/JCR-2413
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta3
>            Reporter: Marcel Reutegger
>             Fix For: 2.0.0
>
>         Attachments: JCR-2413.patch
>
>
> Happens when the indexing queue is checked while creating an initial index. This is probably a regression caused by JCR-2035.
> Caused by: org.apache.lucene.store.AlreadyClosedException: this Directory is closed
>         at org.apache.lucene.store.Directory.ensureOpen(Directory.java:220)
>         at org.apache.lucene.store.FSDirectory.getFile(FSDirectory.java:533)
>         at org.apache.jackrabbit.core.query.lucene.directory.FSDirectoryManager$FSDir.list(FSDirectoryManager.java:149)
>         at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:533)
>         at org.apache.lucene.index.DirectoryIndexReader.open(DirectoryIndexReader.java:115)
>         at org.apache.lucene.index.IndexReader.open(IndexReader.java:316)
>         at org.apache.lucene.index.IndexReader.open(IndexReader.java:263)
>         at org.apache.jackrabbit.core.query.lucene.AbstractIndex.getIndexReader(AbstractIndex.java:245)
>         at org.apache.jackrabbit.core.query.lucene.AbstractIndex.removeDocument(AbstractIndex.java:225)
>         at org.apache.jackrabbit.core.query.lucene.PersistentIndex.removeDocument(PersistentIndex.java:90)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex$DeleteNode.execute(MultiIndex.java:1952)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog(MultiIndex.java:1085)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.checkIndexingQueue(MultiIndex.java:1308)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1177)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1191)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1191)
>         at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1191)
> [...]
> I assume there is an index merge happening at the same time that closes index segments.

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