Hi Michael, Thanks for your feedback. I’m pretty sure that the database is only accessible to a single JVM, but I’ll check it again to be 100% sure. Is there any other possible explanation? I don’t think we’re doing anything too complicated…
In the meantime, it would be great if there was a way to rectify the problem if it happens. Thanks, Martin Iggulden Screen Systems Martin Iggulden | Software Engineer | SCREEN Main Line : +44 1473 831700 | Direct Dial: +44 1473 831700 Fax : +44 1473 830078 martin.iggul...@screensystems.tv<mailto:martin.iggul...@screensystems.tv> Visit us at Broadcast Asia 18-20th June 2019, Suntec Singapore, stand 6J4-02 [http://www.subtitling.com]<http://www.subtitling.com/> [https://www.linkedin.com/company/screen-subtitling-systems-ltd] <https://www.linkedin.com/company/screen-subtitling-systems-ltd> [https://www.youtube.com/channel/Screen Subtitling Systems] <https://www.youtube.com/channel/UCBp2nyUeNbIFz9cD66Ym3AQ> [https://twitter.com/ScreenSystems] <https://twitter.com/ScreenSystems> [cid:SS2979-sasquatch-final-logos_landscape-logo-w236-h56_0717b6a0-e87e-466e-ba39-e63542a11eee.jpg]<https://mysasquatch.info> P Before printing, think about the environment From: Michael Seiferle [mailto:m...@basex.org] Sent: 13 May 2019 10:53 To: Martin Iggulden <martin.iggul...@screensystems.tv> Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Database lock during RESTXQ operation Hi Martin, This error may happen if (1) two different instances of basex try to open/update the very same database. As BaseX uses standard JVM functionality to acquire the Lock it is very likely that indeed to different processes tried to access the very same file. Maybe there is some kind of shared database between your instances that you are trying to access? Best from Konstanz Michael Am 10.05.2019 um 09:17 schrieb Martin Iggulden <martin.iggul...@screensystems.tv<mailto:martin.iggul...@screensystems.tv>>: 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. This message may contain confidential and/or privileged information. If you are not the intended recipient you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. Screen Subtitling Systems Ltd. Registered in England No. 2596832. Registered Office: The Old Rectory, Claydon Church Lane, Claydon, Ipswich, Suffolk, IP6 0EQ