-
Problem report
-
Resolution: Fixed
-
Trivial
-
4.0.0alpha1, 4.0 (plan)
-
None
-
Sprint 23, Sprint 24, Sprint 25
-
0.5
DBcommit no longer set transaction error, so if it fails then it will not be detected and cache will be updated during history synchronization while database will not have the changes.
This can lead to a problems such as trigger being stuck in one state, and missing notifications, though it's possibly a corner case that all other queries succeed but only commit fails.
- caused by
-
ZBX-12925 again. still failed transactions rollback on DB2 backend
- Closed