You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2008/07/10 11:28:31 UTC
[jira] Resolved: (LUCENE-1331) FSDirectory doesn't detect
double-close nor usage after close
[ https://issues.apache.org/jira/browse/LUCENE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1331.
----------------------------------------
Resolution: Fixed
> FSDirectory doesn't detect double-close nor usage after close
> -------------------------------------------------------------
>
> Key: LUCENE-1331
> URL: https://issues.apache.org/jira/browse/LUCENE-1331
> Project: Lucene - Java
> Issue Type: Bug
> Components: Store
> Affects Versions: 1.9, 2.0.0, 2.1, 2.2, 2.3, 2.3.1
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.4
>
> Attachments: LUCENE-1331.patch
>
>
> FSDirectory.close implements logic to ensure only a single instance of FSDirectory per canonical directory exists. This means code that synchronizes on the FSDirectory instance is also synchronized against that canonical directory. I think only IndexModifier (now deprecated) actually makes use of this, but I'm not certain.
> But, the close() method doesn't detect double close, and doesn't catch usage after being closed, and so one can easily get two instances of FSDirectory for the same canonical directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org