000032996 - RSA Access Manager with MSSQL Data Adapter is not compatible with Java Development Kit (JDK) 1.6.0_29

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000032996
Applies ToRSA Product Set: ClearTrust
RSA Product/Service Type: Access Manager
RSA Version/Condition: 6.2 
IssueUsing the MSSQL JDBC jar with JDK 1.6.0_29 breaks the connection from the Aserver and Eserver to the MSSQL database.
The Aserver and Eserver do not throw any exception, but do stop logging at the first attempt to connect to the Aserver/Eserver and never connect.  For example:
Starting connection(s) to SQL:
    mssql ... 15:30:41:506 [dal_conn] [main] - Attempting to open connection.
15:30:42:003 [dal_conn] [main] - Attempting to validate ...
15:30:42:003 [dal_conn] [main] -   Executing query: SELECT COUNT(*) FROM WEB_SERVER_TYPE WHERE 1=2

No further connection logging appears after this.
 
CauseIf the Java Runtime Environment (JRE) is changed from the default version included with Access Manager 6.1 to a standalone version such as Sun Java 1.6.0_29 JDK during an upgrade from Access Manager 6.1 to 6.2, an incompatibility issue can be introduced in JDK 1.6.0_29 where it is not compatible with the MSSQL JDBC driver.
More information can be found in Stack Overflow's article on how the Driver.getConnection hangs using SQLServer driver and Java 1.6.0_29 and on Oracle's discussion forums.

 


 
 
ResolutionThe issue can be resolved by upgrading to a later version of JDK.
NotesIn the next version of Access Manager, Java 1.6 will no longer be supported so customers will then need to upgrade to JDK 1.7 or 1.8.

Attachments

    Outcomes