I am seeing this on release-0.68.0 but I am sure it can occur in other circumstances.
jena [2025-05-07 19:46:24] ERROR Server :: Exception in initialization: Process ID 10 can't open database at location /fuseki/system
/ because it is already locked by the process with PID 11. TDB databases do not permit concurrent usage across JVMs so in order to prevent po
ssible data corruption you cannot open this location from the JVM that does not own the lock for the dataset
jena [2025-05-07 19:46:24] WARN WebAppContext :: Failed startup of context oeje10w.WebAppContext@231cdda8{Apache Jena Fuseki Server,/,b=fi
le:///jena-fuseki/webapp/,a=AVAILABLE,h=oeje10s.SessionHandler@6b70d1fb{STARTED}}
jena org.apache.jena.tdb1.TDB1Exception: Process ID 10 can't open database at location /fuseki/system/ because it is already locked by the pr
ocess with PID 11. TDB databases do not permit concurrent usage across JVMs so in order to prevent possible data corruption you cannot open t
his location from the JVM that does not own the lock for the dataset
Basically something happens that causes jena to crash. I suspect it is because it reaches the memory limit or for other reasons.
After that jena restarts but cannot properly start because it is crashing because of a leftover lock file.
I am seeing this on
release-0.68.0but I am sure it can occur in other circumstances.Basically something happens that causes jena to crash. I suspect it is because it reaches the memory limit or for other reasons.
After that jena restarts but cannot properly start because it is crashing because of a leftover lock file.