Hi Gerald,
Ah I found out how to remove the lock from http://docs.basex.org/wiki/Transaction_Management. Just deleted the upd file.
After that and a restart it seems to be working again, but the reality is that it died on me. I still need clues to figure out why. Are there some tricks, like increasing memory or something, which will prevent it being overwhelmed? (if that's what happened).
It's difficult to say in general what may have causes the faulty behavior. You could check out the information stored in the database logs [1]. Maybe there was one particular query that caused the slowdown?
Exception in thread "Thread-1637" java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(ReentrantReadWriteLock.java:374) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260) at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(ReentrantReadWriteLock.java:1131) at org.basex.core.DBLocking.release(DBLocking.java:219) at org.basex.core.Context.unregister(Context.java:249) at org.basex.core.Command.execute(Command.java:104) at org.basex.core.Command.execute(Command.java:117) at org.basex.server.ClientListener.execute(ClientListener.java:384) at org.basex.server.ClientListener.add(ClientListener.java:355) at org.basex.server.ClientListener.run(ClientListener.java:100)
This usually indicates that the client/server code is used in some unorthodox way. Do you think you can provide us with an SSCCE?
Thanks, Christian