Craig,
what kind of error did you get when initializing FSDirectory ? The fact
that Boolean.getBoolean("disableLuceneLocks") returns false or that the
system property "disableLuceneLocks" is null is not an error. It will
be null, as long as you do not specify the system parameter with
-DdisableLuceneLocks=true or -DdisableLuceneLocks=false during startup.
The other case where disableLuceneLocks is set to true is running the
software on a JVM version 1.1.x. So the documentation is ok when it says
that per default disableLuceneLocks is false.
Bernhard
Craig Stephen wrote:
We've been getting an error when trying to initialize an FSDirectory.
It's on line 48 of the FSDirectory source file. The system property
disableLuceneLocks is null. Now we could set this manually, but it was
working up until about a week ago when we moved our Lucene Wrapper class
to a new package. How is the system property for disableLuceneLocks
normally set? Has anyone had this problem before?
According to the documentation, if you don't set disableLuceneLocks, it
should default to false which is what we want. Any suggestions would be
appreciated.
PS.
We are currently using Lucene 1.4.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
