Re: [Exist-open] Urgent assistance with locking behaviour of existdb

[Pieter L. <pie...@be...>]

Hi Willem,

I would suggest using the latest release or build rather than 6.2.0 and 
checking if the same behavior occurs. My personal experience is that 
lock ups occur when I try to update XQuery resources while they are in 
use. Therefore I do not update the applications while they are running 
production.

Best,
Pieter

On 10/12/2025 1:01 PM, Willem van der Westhuizen wrote:
> Hi
>
> We use existdb extensively to run xqueries on our external databases, 
> couchdb and others. We dont use the existdb datastore for our data.
>
> We used to run on an old 3.3.3 version of existdb, and recently 
> migrated to 6.2. Since then we have found that existdb locks the 
> xquery that is being executed, causing deadlocks that eventually locks 
> up the server. Is there an easy way to tell existdb to revert to the 
> older locking behaviour that does not lock up the xquery being run?
>
>
> Regards
>

-- 
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75G, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web: www.benjamins.com