Long-running campaign loses connection to database

You can set the STALE_CONN_TIMEOUT environment variable to automatically reconnect to a database if the HCL® Campaign or Contact Optimization application loses connection to its back-end database.

An exception message similar to the following occurs: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "<ip>". Communication function detecting the error: "send". Protocol specific error code(s):"32", "*", "0". SQLSTATE=08001.

This issue can occur when a long-running campaign loses connection to its database during a flowchart run.

Set the environment variable STALE_CONN_TIMEOUT for the listener script file for HCL Campaign or Contact Optimization. For example: STALE_CONN_TIMEOUT=<seconds>. The listener script file is rc.unica_ac/cmpServer.bat (for Campaign) and ACOServer.sh/.bat (for Contact Optimization). It is located in <CAMPAIGN_HOME>\bin.

You must restart the listener after adjusting this parameter. If a connection is idle for the number of seconds defined, the connection will be re-opened. If a connection is lost, the following debug message appears in the Campaign flowchart or Contact Optimization server log file: [DB QUERY] Connection is stale, so re-opening db connection!