jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3469) Thread interrupt may result in closed index files
Date Wed, 28 Nov 2012 16:48:59 GMT

    [ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505643#comment-13505643
] 

Alex Parvulescu commented on JCR-3469:
--------------------------------------

One more tiny suggestion :)

Wouldn't it be easier to extend from AbstractIndexingTest and just switch the flag on before
the test and back to its original value after?
This way the test would have its own dedicated workspace, just like the indexing config test
we already have.
Would that make the test simpler?
                
> Thread interrupt may result in closed index files
> -------------------------------------------------
>
>                 Key: JCR-3469
>                 URL: https://issues.apache.org/jira/browse/JCR-3469
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4
>            Reporter: Marcel Reutegger
>            Priority: Minor
>         Attachments: JCR-3469.patch, JCR-3469.patch, JCR-3469-test.patch
>
>
> Interrupting a thread, which is currently performing I/O on Lucene index files, may result
in closed index files. Jackrabbit versions prior to 2.4 didn't have that problem because only
with the update of Lucene to 3.0.3 in Jackrabbit 2.4 the underlying default for the FSDirectory
in Lucene changed from SimpleFSDirectory to NIOFSDirectory. The latter uses a FileChannel
to perform concurrent read operations on a single channel, but because of the way how FileChannel
is specified an interrupt will result in the FileChannel to be closed.
> This was also discussed on the Lucene mailing list. See: http://lucene.markmail.org/thread/ea7mj2kpdvyuesss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message