cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Appmon connectivity with ServiceNow broken after Appmon Upgrade

kyakkala
Inactive

Hi,

We were connecting from Appmom - Service Now using a custom plugin.
We are getting the below SSL Error after our upgrade to 7.0.4 from 6.5.20. Any thoughts?

2017-08-22 15:15:52 WARNING [UserPluginManager@com.dynaTrace.action.ServiceNow.action] [Corp Infrastructure monitors] WINDOWS Corp PROD Server Disk Space C / D Unhealthy INCIDENT SN: javax.net.ssl.SSLException - java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1906)
at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1889)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1410)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:275)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:254)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:123)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at com.dynaTrace.action.ServiceNow.execute(ServiceNow.java:192)
at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:806)
at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:516)
at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:383)
at com.dynatrace.diagnostics.sdk.UserPlugi...

3 REPLIES 3

JamesKitson
Dynatrace Leader
Dynatrace Leader

I imagine this could be a number of things and I don't have enough experience to know how to correct it but it looks like it could be related to the keystore you're using for the connection being unavailable possibly do to a permissions issue, or it could be invalid for some reason. That error about "the trustAnchors parameter must be non-empty" comes up quite a bit in a search.

https://stackoverflow.com/questions/6784463/error-...

James

kyakkala
Inactive

I even tried using old(6.5) Java files and cacerts instead of 7.0 files and still no luck in getting this plugin to work.

kyakkala
Inactive

This issue was caused because of
the trustAnchors parameter missing in the keystore and adding it to
Dynatrace services(frontend and server) ini files fixed the issue.

-Djavax.net.ssl.trustAnchors=D:\Program
Files\dynaTrace\Dynatrace 7.0\jre\lib\security\cacerts