[jira] [Commented] (JENA-1104) LockObtainFailedException for text index

["Joachim Neubert (JIRA)" <ji...@apache.org>]

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

Joachim Neubert commented on JENA-1104:
---------------------------------------

Ah - perhaps the issue is triggered by an error during the build of the text index.

I'll investigate and provide further information.


> LockObtainFailedException for text index
> ----------------------------------------
>
>                 Key: JENA-1104
>                 URL: https://issues.apache.org/jira/browse/JENA-1104
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: Fuseki
>    Affects Versions: Fuseki 2.3.1
>         Environment: CentOS 5.11
> Java 1.8.0_45-b14
> Tomcat 7.0.62
>            Reporter: Joachim Neubert
>
> When starting Fuseki2 under Tomcat, on Centos 5 I get an exception which I have not seen on Centos 7:
> {quote}
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.jena.fuseki.server.FusekiServerListener
> org.apache.jena.assembler.exceptions.AssemblerException: caught: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/opt/thes/var/gn
> d/2015-10-13/tdb_lucene/write.lock: java.nio.channels.OverlappingFileLockException
>   doing:
>     root: file:///opt/fuseki2/run/configuration/gnd.ttl#gndIndex with type: http://jena.apache.org/text#TextIndexLucene assembler class: class org.apache.jena.query.tex
> t.assembler.TextIndexLuceneAssembler
>     root: file:///opt/fuseki2/run/configuration/gnd.ttl#gnd with type: http://jena.apache.org/text#TextDataset assembler class: class org.apache.jena.query.text.assembl
> er.TextDatasetAssembler
>         at org.apache.jena.assembler.assemblers.AssemblerGroup$PlainAssemblerGroup.openBySpecificType(AssemblerGroup.java:138)
> ...
> {quote}
> The very strange thing is that tomcat actually *has* created the write.lock file in that directory (which I had removed before).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)