Hi Mahadevan,
I think you hit a new bug that I was able to reproduce.
The problem is an incorrect handling of operation return code when
there is an error in SLAPI_PLUGIN_BE_TXN_POST_ADD_FN.
When the operation succeeds in the DB, DS (as a master) updates the
CL and RUV in
Hello all,
I´m trying to compile a new version of 389 DS (389-ds-base-1.3.0.4) and I´m
getting this error:
gcc -DHAVE_CONFIG_H -I. -DBUILD_NUM=\2013.168.127\ -DVENDOR=\389
Project\ -DBRAND=\389\ -DCAPBRAND=\389\ -UPACKAGE_VERSION
-UPACKAGE_TARNAME -UPACKAGE_STRING -UPACKAGE_BUGREPORT
I do not know why your environment is prone to trigger db_deadlock (lot of
replica agreements, VM, slow disks...).
I think the best way to progress is that you fill a ticket/bug so that we may
track the issue. Note this bug is possibly affecting all operations
(ADD/MOD/MODRDN/DEL)
-
Hi
I do not know why your environment is prone to trigger db_deadlock (lot of
replica agreements, VM, slow disks...).
I think the best way to progress is that you fill a ticket/bug so that we may
track the issue. Note this bug is possibly affecting all operations
(ADD/MOD/MODRDN/DEL)
---
Hi
