We just encountered a stuck lock on a BaseX database. It was during repeated calls to a RESTXQ operation that modifies the database. The operations were working OK, then one returned an error:

[db:lock] Database 'd7c552cc-1f5e-47dc-ba91-37054695aabf' is currently opened by another process.

This error then appeared for any further attempt to update the database, and persisted for several days (although it seems to have cleared now).

It’s possible that two updates were being processed concurrently, but they would have been processed by the same Java VM because the RESTXQ server is the only active interface to the database.

We have seen this error before, but it’s difficult to reproduce.

Do you know how this might have happened? And is there a procedure for clearing down an erroneous database lock if it happens?

We are running BaseX version 9.1.2.

Thanks,

Martin Iggulden

Screen Systems