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

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

One further issue,

If the calls are not too rapid, then it does not happen. But many 
different calls to the same xquery will increase the likelihood of a lockup.

Willem

On 2025/10/15 10:30, Juri Leino wrote:
> Hi Willem!
>
> The behaviour you are describing is usually a sign for an attempt to 
> replace/update a running XQuery.  If this is the case the easiest 
> solution is to make sure that the query you want to replace / change 
> is not being run at the moment.
>
> I agree that we should investigate if we even have to lock the XQuery 
> in the first place. But that is a separate discussion.
>
> Regards,
> Juri
>
> On 12.10.25 13:01, 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
>>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open