Unable to acquire JDBC Connection

Hello Infor, we have been facing recently an issue with sql database connection point happening on the PRD system randomly where sometimes the connection is failing with the following error: Unable to acquire JDBC Connection. 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: "Unexpected rethrowing".
Any idea what we are missing?. thank you

Find more posts tagged with

ION Connect

Accepted answers

All comments

unknown

hello any hints on the above?could it be an issue with the jdbc driver that ION uses?

thank you,

Kevin Heiman

Have you reviewed the Ent Connector log? Is this where you picked up the message above?

How frequently does it occur vs how frequently does it succeed? Is the Ent Conn in proximity to the SQL server?

In general the issue would be with the Ent Conn ability to connect to the target database. Ent Connector is reporting what the JDBC driver reported. We have no control over the pathway from Ent Conn to the SQL server.

There are versions of the SQL JDBC drivers, have you looked at using the latest? Are there setting you can supply to compensate for your network?

Do these error occur when network is saturated or failing?

Do you see other errors on the SQL server logs?

Can you have a test running that tries a JDBC connection to the DB in parallel as a comparison?

unknown

Hello Kevin, the error was thrown from ion as an error bod when the message reached the database connection point. The issue occurrence is very rare. it has happened 4 times so far since 3 months. When we resbumit the message, it will successfully make it to the database without any issues. So the issue is very random and very rare but it is happening and we have no logs whatsoever on what is causing it.

Kevin Heiman

Correct, the failure will bubble up as an confirm BOD and can be monitored via ERROR in a workflow, or the error inquiry screen.

Suggest you review the logs on the enterprise connector. You can raise the logging level but with it being that infrequent, you would gather large amount of logging.

This would appear to be a network issue on your enterprise as that is where the JDBC driver runs from. The connection to it from ION is over SQS.

Review you are using the latest drivers. But also work with your network team to see if they can monitor.

You did not provide some of the other questions, like; how many are successful? how frequently is the SQL invoked? is the occurrence at the same time of day a symptom? What is the proximity to the SQL server?

Copyright © 2025 Infor. All rights reserved.