|Applies To||RSA Product Set: ClearTrust|
RSA Product/Service Type: Access Manager
RSA Version/Condition: 6.2
|Issue||Using 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:
No further connection logging appears after this.
|Cause||If 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.
|Resolution||The issue can be resolved by upgrading to a later version of JDK.|
|Notes||In 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.|