Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When I first developed Mirroring, I assumed sending the mirrored ACK on a aferACK and disconnected from any other transactions would be enough, with the caveat you could get a duplicate delivery on the target mirror in case of failures.
I got some complains that this is not safe enough from some users, and I'm making this now idempotent.
I took an overal mirroring hardening approach and I'm improving test coverage for this improvement.
Attachments
Issue Links
- links to