WCC Machine status shows "Missing" & Datasources message ' trustAnchors parameter must be non-empty'

Document ID : KB000118956
Last Modified Date : 02/11/2018
Show Technical Document Details
Issue:
 On the Agent List tab in WCC, one of the agent's Machine Status shows "Missing". Clicking on DataSources shows the following message:
"InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty"

There are several error messages related to the datasource error above in CA-wcc.log file.  

Repeated every few minutes:

INFO   | jvm 1    | 2018/10/22 13:56:12 |    86367 |     at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
INFO   | jvm 1    | 2018/10/22 13:57:13 |    86428 | Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
INFO   | jvm 1    | 2018/10/22 13:57:13 |    86428 | Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Environment:
ALL components are on the same machine
Oracle 12C Linux
AE: 11.3.6 SP7
WCC: 11.4 SP6 (uses Derby)
EEM: 12.6 1 
Cause:
The wrapper.conf file needed to also have the 'keystorepass' password from the server.xml file.
Resolution:
It appears the keystorepass property changed in the server.xml file. 

Do the following to add that password to the wrapper.conf file : 

1. Stop both CA-wcc-services and CA-wcc services. 
2. Take the backup of wrapper.conf file present at <WCC_INSTALL_LOCATION>\tomcat\conf. 
3. Open the wrapper.conf file present at <WCC_INSTALL_LOCATION>\tomcat\conf. 
4. Search for "wrapper.java.additional.14=-Djdk.tls.ephemeralDHKeySize=2048" in the file. 
5. After the above property add more line - 
wrapper.java.additional.15=-Djavax.net.ssl.trustStorePassword=<keystore Password> 
6. Replace <keystore Password> with the value of keystorePass property present in the server.xml file. This server.xml is present at <WCC_INSTALL_LOCATION>\tomcat\conf. 
7. Start both CA-wcc-services and CA-wcc. 
8. . Check if the problem still persists.