Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
After installing java agent we observe application db calls were not reaching database due to the below SSL error.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Server chose TLSv1, but that protocol version is not enabled or not supported by the client.". ClientConnectionId:32851fac-b35c-4e22-b400-802110ad047b
We also tried to connect the controller with a non-https controller host in controller-info.xml the following error is seen.
[AD Thread Pool-Global0] 05 Dec 2019 14:43:05,100 ERROR ConfigurationChannel - HTTP Request failed: HTTP/1.1 302 Found
[AD Thread Pool-Global0] 05 Dec 2019 14:43:05,100 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host
We don't have the DB that supports the TLSv1 protocol. Can you please help us to disable this protocol or any other approach to resolve this issue.
The app is working and connecting to DB without the provided java agent jar.
You need to set the appdynamics.agent.tls.allowedAlgorithms system property on the JVM command line to allow use of TLSv1:
Thank you for your response.
I would like to elaborate on the exact issue I'm facing:
The DB I'm using serves all the network calls without any security i.e SSL etc. It's built-in that way. Right now after placing the java agent Jar file in our App server all the network calls were being encrypted with TLSv1 security protocol.
Due to the above change, all the requests from the application to the database are failing with the error shown in our previous message.
My question here is, We do want to use the AppDynamics performance monitoring with our App and DB but we want to disable the security shipped in with it. Is there any other procedure we could follow to overcome this?
Else, Please let me know if I am missing something or any other setup that needs to be done to overcome the same.
Your help is deeply appreciated.
Thanks in advance,
That is a most surprising observation!
Without digging deeper into what is going on, I am not sure what to suggest. The best path forward will be to open a support ticket and have a support engineer dig into the details of what is going on.