[
https://issues.apache.org/jira/browse/JCR-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes resolved JCR-3818.
-------------------------------
Resolution: Fixed
> Use SimpleFSDirectory by default
> --------------------------------
>
> Key: JCR-3818
> URL: https://issues.apache.org/jira/browse/JCR-3818
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Unico Hommes
> Assignee: Unico Hommes
> Fix For: 2.8.1, 2.9.1
>
>
> We have recently discovered a problem with the way Lucene index files
> are accessed in Jackrabbit 2 when running with the default repository
> configuration.
> For reading and writing its indexes Lucene can use different
> implementations. By default implementations are preferred based on
> the java.nio package. These implementations however have the following
> drawback:
> "Accessing this class either directly or indirectly from a thread
> while it's interrupted can close the underlying file descriptor
> immediately if at the same time the thread is blocked on IO. The file
> descriptor will remain closed and subsequent access to [this class]
> will throw a ClosedChannelException."
> So if the application at one point sets an interrupt on a thread that
> at the same time is accessing a Lucene index file, the file channel is
> closed and subsequent access will throw an exception. If that happens,
> the application needs to be reinitialized before the Lucene index can
> be used again.
> Refer to the discussion of this issue on the lucene developer list at [1].
> To say the least, this is very brittle behaviour.
> Fortunately Jackrabbit SearchIndex can be configured with a parameter
> to use a different Lucene IO access implementation that does not
> suffer from this issue (useSimpleFSDirectory which causes Jackrabbit
> to use a FSDirectory that is based on access via
> java.io.RandomAccessFile).
> 1. http://marc.info/?l=lucene-dev&m=126466874929360&w=4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
