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

[Willem v. d. W. <wi...@kw...>]

Hi,

In our case we are not updating when the locking occurs. We simply call 
the rest services, and then they call other rest services outside of 
exist. We use local curl statements to call the rest services, and that 
causes the lockup. And we can see that the waiting for locks are 
growing. It seems that if the rest services are called from the outside, 
and they themselves call rest services, the later versions lock up. And 
when the server reached about 160 processed it always crashes.    I have 
attached the screen shots of the monex. If you look at the logs, its 
frozen, nothing running.



On 2025/10/14 11:23, Pieter Lamers via Exist-open wrote:
> 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
>>
>