There is a process which uses the Process Automation database operator to update 3 custom tables in MDB . But this operator often fails due to a dropped database connection with the following error in c2o.log :
-----------------------------------------
ERROR [com.optinuity.c2o.service.serviceoperation.jdbcserviceoperation.RunnerJDBCSelectServiceOperation] [be-b4a95a13c730] Could not connect to the database; The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.".
at com.optinuity.c2o.service.serviceoperation.jdbcserviceoperation.JDBCWrapper.getDBConnection(JDBCWrapper.java:1256)
at com.optinuity.c2o.service.serviceoperation.jdbcserviceoperation.JDBCGenericWrapper.executeSQL(JDBCGenericWrapper.java:209)
CA Process Automation 4.3
Java 8
SSL
In some cases when using Java 8 the secure negotiation will use TLSv1.2 and sometimes TLSv1.
The times that TLSv1.2 is used, the connection will fail.
Add the following Java parameter to the c20svcw.conf file (located in /PAM/server/c2o/bin)
-Djdk.tls.client.protocols=TLSv1
at the end of the file. It will look like
wrapper.java.additional.14=-Djdk.tls.client.protocols=TLSv1
Make sure to increment the number (13,14, 15 etc) appropriately based on the previous parameter.
Process Automation will need to be restarted after this change.