Re: [bdbxml] couldn't open container twice

Dmitriy Kargapolov <xoid@...> writes:

> Another consideration:
> I ran two identical processes on same db/container.
> Each process opens container, performs some modification, then closes it.
> Everything is done with transaction support.
> After couple minutes of normal processing both proc. are stuck.
> Backtrace in the GDB shows same place where they are waiting:
> __db_tas_mutex_lock():
> 

Actually the problem was in the db build option I used:
--with-berkeleydb-conf=--with-mutex=HP/msem_init
Once I took it out, POSIX/pthreads/library was used
instead of HP/msem_init, and "deadlock" error has gone.

Something is wrong with HP/msem_init-based db implementation
under HP-UX B.11.11...




------------------------------------------
To remove yourself from this list, send an
email to [email protected]