You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jan Haderka (JIRA)" <ji...@apache.org> on 2009/01/26 17:49:59 UTC
[jira] Created: (JCR-1955) Lucene 2.3.2 - AlreadyClosedException:
this IndexReader is closed
Lucene 2.3.2 - AlreadyClosedException: this IndexReader is closed
------------------------------------------------------------------
Key: JCR-1955
URL: https://issues.apache.org/jira/browse/JCR-1955
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: indexing
Affects Versions: 1.5.2
Reporter: Jan Haderka
Attachments: stacktrace.txt
When deploying application on Websphere using Jackrabbit 1.5.2 and Lucene 2.3.2 I just ran into issue already described at http://www.nabble.com/Lucene-AlreadyClosedException-tt15049132.html#a15049132
When I change lucene back to 2.2.0 and rebuild indexes, problem goes away.
I don't seem to be able to reproduce the issue in other environment then Websphere app server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1955) Lucene 2.3.2 - AlreadyClosedException:
this IndexReader is closed
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668030#action_12668030 ]
Thomas Mueller commented on JCR-1955:
-------------------------------------
What about adding the version number (of the relevant module) to the exception? We would need exception factories, but it would make support much easier: no need to ask about the version, and less confusion if multiple versions are in the classpath.
> Lucene 2.3.2 - AlreadyClosedException: this IndexReader is closed
> ------------------------------------------------------------------
>
> Key: JCR-1955
> URL: https://issues.apache.org/jira/browse/JCR-1955
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.5.2
> Reporter: Jan Haderka
> Attachments: stacktrace.txt
>
>
> When deploying application on Websphere using Jackrabbit 1.5.2 and Lucene 2.3.2 I just ran into issue already described at http://www.nabble.com/Lucene-AlreadyClosedException-tt15049132.html#a15049132
> When I change lucene back to 2.2.0 and rebuild indexes, problem goes away.
> I don't seem to be able to reproduce the issue in other environment then Websphere app server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1955) Lucene 2.3.2 - AlreadyClosedException:
this IndexReader is closed
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1955.
-----------------------------------
Resolution: Invalid
The line numbers of the jackrabbit classes in the stacktrace indicate that you are using 1.4.x instead of the claimed version 1.5.2. Jackrabbit 1.4.x only works with Lucene 2.2.0.
Please check your classpath for jar files from old jackrabbit releases.
> Lucene 2.3.2 - AlreadyClosedException: this IndexReader is closed
> ------------------------------------------------------------------
>
> Key: JCR-1955
> URL: https://issues.apache.org/jira/browse/JCR-1955
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.5.2
> Reporter: Jan Haderka
> Attachments: stacktrace.txt
>
>
> When deploying application on Websphere using Jackrabbit 1.5.2 and Lucene 2.3.2 I just ran into issue already described at http://www.nabble.com/Lucene-AlreadyClosedException-tt15049132.html#a15049132
> When I change lucene back to 2.2.0 and rebuild indexes, problem goes away.
> I don't seem to be able to reproduce the issue in other environment then Websphere app server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1955) Lucene 2.3.2 - AlreadyClosedException:
this IndexReader is closed
Posted by "Jan Haderka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Haderka updated JCR-1955:
-----------------------------
Attachment: stacktrace.txt
Attaching the relevant stacktrace. The issue can be reproduced always in Websphere app server.
> Lucene 2.3.2 - AlreadyClosedException: this IndexReader is closed
> ------------------------------------------------------------------
>
> Key: JCR-1955
> URL: https://issues.apache.org/jira/browse/JCR-1955
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.5.2
> Reporter: Jan Haderka
> Attachments: stacktrace.txt
>
>
> When deploying application on Websphere using Jackrabbit 1.5.2 and Lucene 2.3.2 I just ran into issue already described at http://www.nabble.com/Lucene-AlreadyClosedException-tt15049132.html#a15049132
> When I change lucene back to 2.2.0 and rebuild indexes, problem goes away.
> I don't seem to be able to reproduce the issue in other environment then Websphere app server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.