I ran the code from master (no changes) against loadtest (no parameters, so 10 threads) and I get a coredump within 30 seconds.
citserver[43011]: bdb: bdb_delete(00): BDB0068 DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock I will have to try again with a clean easyinstall just in case my build environment is causing something different. Can you try again and look in the system log for "DEADLOCK" or "Core Dump". As a side note, when I run loadtest, I get a bunch of error messages in the system log from citserver about NULL bodies. I don't think they are related to the deadlocks, but not sure why I am getting them. Do you get this too? msgbase: ERROR; attempt to save message with NULL body > Mon Jan 06 2025 05:06:01 UTC from HarlowSolutions Subject: Re: >Database Deadlock Handling > > > >I will try loadtest and see if I can recreate. If not I will see about >modifying it to make it recreate. > >As for the configuration settings, the workers are started and added in >threads.c I think it looks at the upper limit, but does not do >anything with a lower limit. Both are probably useful. > > > >
