Informix - Problem description
Problem IT30739 | Status: Closed |
SMARTTRIGGER: SMART TRIGGER CLASS IS NOT HANDLING IFX_ERROR SENTFROM THE SERVER | |
product: | |
IBM JDBC / 5724I3501 / 410 - Informix 4.10 | |
Problem description: | |
When ER stopped, the server will send {"ifx_error":"Enterprise Replication not active"} The smart trigger code is not checking for and ifx_error event label those the errors get ignored ad they don't get propagated to the listeners. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix JDBC 4.10.JC12 and earlier versions. * **************************************************************** * PROBLEM DESCRIPTION: * * When ER stopped, the server will send * * {"ifx_error":"Enterprise * * Replication not active"}. * * * * The smart trigger code is not checking for an ifx_error * * event * * label. Those errors get ignored and they don't get * * propagated * * to the listeners. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix JDBC 4.10.JC12 and earlier versions. * **************************************************************** * PROBLEM DESCRIPTION: * * When ER stopped, the server will send * * {"ifx_error":"Enterprise * * Replication not active"}. * * * * The smart trigger code is not checking for an ifx_error * * event * * label. Those errors get ignored and they don't get * * propagated * * to the listeners. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Comment | |
Upgrade to Informix JDBC 4.10.JC14 or later. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.10.2019 27.02.2020 27.02.2020 |
Problem solved at the following versions (IBM BugInfos) | |
4.10.JC14 | |
Problem solved according to the fixlist(s) of the following version(s) |