From: Ralf J. <ral...@gm...> - 2010-12-22 13:49:08
|
Hi, after updating to revision 13430, I occasionally see locking errors in the log that have me worried. I also just lost my whole DB as it got caught in some deadlock or whatever (would only reply to SIGKILL), and left the files in an invalid state. I can reproduce the error messages by clearing my data folder and starting eXist on a new empty database. The message looks like this: 2010-12-22 14:46:40,054 [WrapperListener_start_runner] WARN (MultiReadReentrantLock.java [releaseWrite]:337) - Possible lock problem: a thread released a write lock it didn't hold. Either the thread was interrupted or it never acquired the lock. java.lang.Throwable at org.exist.storage.lock.MultiReadReentrantLock.releaseWrite(MultiReadReentrantLock.java:337) at org.exist.storage.lock.MultiReadReentrantLock.release(MultiReadReentrantLock.java:277) at org.exist.storage.txn.Txn.releaseAll(Txn.java:62) at org.exist.storage.txn.TransactionManager.commit(TransactionManager.java:182) at org.exist.config.Configurator.save(Configurator.java:836) at org.exist.config.Configurator.parse(Configurator.java:735) The complete log of an initial startup is attached. Kind regards, Ralf Jung |