Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I resolve my Java Agent’s failure to respond after an upgrade?

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
Revision #:
6 of 6
Last update:
‎01-26-2020 10:44 AM
Updated by:
 
Labels (1)


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
0 Kudos