View Revisions: Issue #4538
| Summary | 0004538: Suppress first deadlock, FK, or protocol violation error to allow retry | ||
|---|---|---|---|
| Revision | 2020-09-14 18:00 by elong | ||
| Description | Suppress logging at ERROR level for first deadlock, foreign key, or protocol violation message received on a row in a batch. If the retry succeeds, there should be no ERROR level message in the log and the error_flag should remain off in the sym_outgoing/incoming_batch tables. This will prevent the user from being notified of errors that were successful after retrying once. If the retry is not successful, the log messages will go to ERROR level and the error_flag will be set. Standardize the deadlock sql code as -911 in the sym_outgoing/incoming_batch tables so either side knows a deadlock occurred regardless of platform. Initial implementation for Oracle, MySQL, MariaDB, SQL-Server, Postgres, Sybase, DB2, and FIrebird. |
||
| Revision | 2020-09-11 00:03 by elong | ||
| Description | Suppress logging at ERROR level for first deadlock message received on a row in a batch. Standardize the deadlock sql code as -911 in the sym_outgoing/incoming_batch tables so either side knows a deadlock occurred regardless of platform. Initial implementation for Oracle, MySQL, MariaDB, SQL-Server, Postgres, Sybase, DB2, and FIrebird. | ||