Various Java Exception errors when trying to use Java SSL with AT-TLS pointing to ACF2 or Top Secret keyring
Article ID: 248650
Updated On:
Products
Issue/Introduction
Various DB2 stored procedures are using different DB2XML functions to communicate to an external web server. Some of these procedures work when the AT-TLS policy was activated to make SOAP calls function properly. However, other stored procedures stopped working. These stored procedures invoke Java SSL.
The ones that fail to work throw a number of errors in the following order. Once one is resolved, the next error appears:
java.lang.Exception: Truststore file does not exist
java.io.IOException: The private key of certificate_name is not available or no authority to access the private key
javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
Why are these errors occurring and how can the last error message be resolved?
Environment
Release : 16.0
Component : ACF2 for z/OS
Resolution
Java SSL connections are not currently supported through AT-TLS. Java always wants to do its own SSL handshaking/certificate handling and if a site is attempting to push that traffic through AT-TLS, it will not work. IBM Java support will need to be contacted for further information.
Feedback
