Joachim Neubert created JENA-1136:
-------------------------------------

             Summary: Stopping Fuseki under Tomcat seems not to remove tdb and 
lucene locks
                 Key: JENA-1136
                 URL: https://issues.apache.org/jira/browse/JENA-1136
             Project: Apache Jena
          Issue Type: Bug
          Components: Fuseki
    Affects Versions: Fuseki 2.4.0
         Environment: CentOS 5.x
            Reporter: Joachim Neubert


When restarting Tomcat with the latest Fuseki snapshot 
(apache-jena-fuseki-2.4.0-20160209.095958-47.tar.gz), the application can't be 
started:

[2016-02-10 06:48:04] Config     INFO  FUSEKI_HOME=/opt/fuseki
[2016-02-10 06:48:04] Config     INFO  FUSEKI_BASE=/opt/fuseki2/run
[2016-02-10 06:48:04] Config     INFO  Shiro file: 
file:///opt/fuseki2/run/shiro.ini
[2016-02-10 06:48:04] Config     INFO  Context path = /fuseki
[2016-02-10 06:48:04] Config     INFO  Configuration file: 
/opt/fuseki2/run/config.ttl
[2016-02-10 06:48:04] Server     ERROR Exception in initialization: Can't open 
database at location /opt/apache-jena-fuseki-2.4.0-SNAPSHOT/run/system/ as it 
is already
locked by the process with PID 23588.  TDB databases do not permit concurrent 
usage across JVMs so in order to prevent possible data corruption you cannot 
open this loc
ation from the JVM that does not own the lock for the dataset
Feb 10, 2016 6:48:04 AM org.apache.catalina.core.StandardContext startInternal

After manually deleting all tdb.lock files, it barks on the text indexes:

[2016-02-10 06:53:49] Config     INFO  FUSEKI_HOME=/opt/fuseki
[2016-02-10 06:53:49] Config     INFO  FUSEKI_BASE=/opt/fuseki2/run
[2016-02-10 06:53:49] Config     INFO  Shiro file: 
file:///opt/fuseki2/run/shiro.ini
[2016-02-10 06:53:49] Config     INFO  Context path = /fuseki
[2016-02-10 06:53:49] Config     INFO  Configuration file: 
/opt/fuseki2/run/config.ttl
[2016-02-10 06:53:51] Server     ERROR Exception in initialization: caught: 
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: 
NativeFSLock@/opt/thes/var/stw/9.0/tdb_lucene/write.lock

After deleting these manually, too, Fuseki starts. (So I've added the cleanup 
temporarily to my tomcat stop function in the service definition file.)




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

Reply via email to