lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Kerkhoff (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-812) Unable to set LockFactory implementation via ${org.apache.lucene.store.FSDirectoryLockFactoryClass}
Date Thu, 22 Feb 2007 14:06:05 GMT
Unable to set LockFactory implementation via ${org.apache.lucene.store.FSDirectoryLockFactoryClass}
---------------------------------------------------------------------------------------------------

                 Key: LUCENE-812
                 URL: https://issues.apache.org/jira/browse/LUCENE-812
             Project: Lucene - Java
          Issue Type: Bug
          Components: Store
    Affects Versions: 2.1
            Reporter: Matthias Kerkhoff


While trying to move from Lucene 2.0 to Lucene 2.1 I noticed a problem with the LockFactory
instantiation code.
During previous tests we successfully specified the LockFactory implementation by setting
the property
${org.apache.lucene.store.FSDirectoryLockFactoryClass} to "org.apache.lucene.store.NativeFSLockFactory".
This does no longer work due to a bug in the FSDirectory class. The problem is caused from
the fact that this
class tries to invoke the default constructor of the specified LockFactory class. However
neither NativeFSLockFactory
nor SimpleFSLockFactory do have a default constructor.

FSDirectory, Line 285:
          try {
            lockFactory = (LockFactory) c.newInstance();          
          } catch (IllegalAccessException e) {
            throw new IOException("IllegalAccessException when instantiating LockClass " +
lockClassName);
          } catch (InstantiationException e) {
            throw new IOException("InstantiationException when instantiating LockClass " +
lockClassName);
          } catch (ClassCastException e) {
            throw new IOException("unable to cast LockClass " + lockClassName + " instance
to a LockFactory");
          }

A possible workaround is to not set the property at all and call FSDirectory.setLockFactory(...)
instead. 

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