An application passed bad arguments to a DB2 Native Stored Procedure using a secure JDBC. The failure was due to a -440 SQL error. Detector didn't report the -440 error until the JDBC connection was changed from secure to unsecure. Why did Detector not capture the secure JDBC -440 SQL Error?
Release : 20.0
Component : CA Detector for DB2 for z/OS
The SSL processing rejected the request due to an authentication failure, which results in the -440. Because the authentication failed, no DB2 activity occurred on the request, and therefore Detector never saw the error, as Detector was never invoked.