JDBC: Cannot create PoolableConnectionFactory Communications link failure when attempting to connect to a MySQL endpoint

book

Article ID: 206455

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

We have a new MySQL Server 5.7.23 target. We used Connector Xpress to create a custom connector to this target and deploy the connector.

We followed https://knowledge.broadcom.com/external/article?articleId=134411 to manually deploy the required jar under the relevant folders.

When we test the connection and the JDBC URL using Connector Xpress, it works as expected

When we try to define a new endpoint using Provisioning Manager, the following error is observed

20210105:163543:TID=000974:Add       :S687:E675:F: FAILURE: Connector Server Add (eTDYNDirectoryName=MySQLEndpoint)
20210105:163543:TID=000974:Add       :S687:E675:F:     rc:  0x0035 (DSA is unwilling to perform)
20210105:163543:TID=000974:Add       :S687:E675:F:     msg: Connector Server Add failed: code 53 (UNWILLING_TO_PERFORM): failed to a
20210105:163543:TID=000974:Add       :S687:E675:F:+dd entry eTDYNDirectoryName=MySQLEndpoint,eTNamespaceName=MySQL,dc=im,dc=etasa: 
20210105:163543:TID=000974:Add       :S687:E675:F:[email protected]: JDBC: Cannot create PoolableConnectionFactory (Communications l
20210105:163543:TID=000974:Add       :S687:E675:F:+ink failure
20210105:163543:TID=000974:Add       :S687:E675:F: 
20210105:163543:TID=000974:Add       :S687:E675:F: The last packet successfully received from the server was 45 milliseconds ago.  T
20210105:163543:TID=000974:Add       :S687:E675:F:+he last packet sent successfully to the server was 43 milliseconds ago.) (ldaps:/
20210105:163543:TID=000974:Add       :S687:E675:F:+/myjcs.domain.com:20411)

Cause

Incorrect driver / JDBC URL combination

Environment

Release : 14.3
Component : IdentityMinder(Identity Manager)

Resolution

1. Utilizing a compatible version driver (ie mysql-connector-java-5.1.40-bin.jar)

2. Adjusting the connection URL. We have verified that if the URL is incorrect with the target, it creates these problems.
We used the following jdbc URL: mysql: //<hostname>:<port>/xxx? SessionVariables = sql_mode = 'ANSI'