lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LUCENE-674) Error in FSDirectory if java.io.tmpdir incorrectly specified
Date Mon, 22 Sep 2008 18:04:44 GMT

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

Michael McCandless resolved LUCENE-674.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1

Newer versions of Lucene (since 2.1) now store the lock file in the index directory by default.

> Error in FSDirectory if java.io.tmpdir incorrectly specified
> ------------------------------------------------------------
>
>                 Key: LUCENE-674
>                 URL: https://issues.apache.org/jira/browse/LUCENE-674
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 2.0.0
>         Environment: Reported on a Linux system under Tomcat
>            Reporter: Ryan Holliday
>            Priority: Minor
>             Fix For: 2.1
>
>
> A user of the JAMWiki project (http://jamwiki.org/) reported an error with the following
stack trace:
> SEVERE: Unable to create search instance /usr/share/tomcat5/webapps/jamwiki-0.3.4-beta7/test/base/search/indexen
> java.io.IOException: Cannot create directory: /temp
>         at org.apache.lucene.store.FSDirectory.init(FSDirectory.java:171)
>         at org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:141)
>         at org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:117)
>         at org.jamwiki.search.LuceneSearchEngine.getSearchIndexPath(LuceneSearchEngine.java:318)
> The culprit is that the java.io.tmpdir property was incorrectly specified on the user's
system.  Lucene could easily handle this issue by modifying the FSDirectory.init() method.
 Currently the code uses the index directory if java.io.tmpdir and org.apache.lucene.lockDir
are unspecified, but it could use that directory if those values are unspecified OR if they
are invalid.  Doing so would make Lucene a bit more robust without breaking any existing installations.

-- 
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


Mime
View raw message