cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Jason.Riddell
AppDynamics Team

How can I repair an SSL error resulting from upgrading the Java Agent?

 

Problem

When upgrading the Java Agent from version 4.5.10 to 4.5.16, the following WebSphere error occurs:

[1/6/20 15:30:05:558 CET] 00000112 ResponseCreat E Error occured:
example.facade.service.exception.InternalErrorException: example.code.SocketErrorException: Unable to perform handshake - [javax.net.ssl.SSLHandshakeException] No appropriate protocol, may be no appropriate cipher suite specified or protocols are deactivated
at example.facade.service.inf.serviceProvider.service(SampleServiceProvider.java:31)
...
Caused by: example.code.SocketErrorException: Unable to perform handshake - [javax.net.ssl.SSLHandshakeException] No appropriate protocol, may be no appropriate cipher suite specified or protocols are deactivated
at sample.code.ip.VerifyClient.sendAndReceive(VerifyClient.java:3553)
at sample.code.ip.VerifyClient.doMethod(VerifyClient.java:3541)
at sample.code.ip.VerifyClient.getUserInfo(VerifyClient.java:2058)
at example.facade.service.impl.user.sample.SampleUserInfoProvider$1.run(SampleUserInfoProvider.java:33)

 

Solution

Resolve the issue by setting the appdynamics.agent.tls.allowedAlgorithms system property on the JVM command line to allow the use of SSLv3: 

System Property: -Dappdynamics.agent.tls.allowedAlgorithms=SSLv3

Alternatively, if you have older SSL Ciphers installed internally, then set the sys add to allow the use of TLSv1 as follows: 

System Property: -Dappdynamics.agent.tls.allowedAlgorithms=TLSv1

 

Resource Summary

Java Agent Configuration Properties: Configure allowed TLS/SSLP Protocols

Version history
Last update:
‎01-26-2020 10:44 AM
Updated by:
Join Us On December 10
Learn how Splunk and AppDynamics are redefining observability


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here