- You have a client application that uses Java and Microsoft JDBC Driver for SQL Server to connect to SQL Server.
- You upgrade Oracle Java Runtime Environment (JRE) to version 6 Update 29 or a later version.
- After you upgrade JRE, you can no longer connect to SQL Server.
In this scenario, JDBC Driver might stop responding when it is trying to open the connection. Additionally, JDBC Driver fails immediately and a call stack is generated if one of the following methods is used to encrypt connections:
- The Encrypt property is set to True in the connection URL.
- SQL Server is configured to force encryption.
- You may experience this issue if you use third-party implementations of Secure Sockets Layer (SSL)/Transport Layer Security (TLS) that contain the same behavioral change as JRE version 6 Update 29 and later versions. This change in behavior fixes a specific security issue known as "BEAST." If you are unsure whether a third-party product contains an implementation of SSL/TLS that includes this change, contact the product’s vendor.
- Any data access provider that uses the OpenSSLlibrary may also cause this issue.
Service pack information for SQL Server 2008 R2To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2008 R2
Cumulative update information
SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 3 for SQL Server 2008 SP3The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
- Use an earlier version of Oracle JRE than JRE version 6 Update 29.
- Disable SSL record splitting at the JRE level.
- This method might have security implications for HTTP communications.
- For more information about this procedure, you can contact.
This problem was first corrected in SQL Server 2008 R2 Service Pack 2.
Article ID: 2653857 - Last Review: May 14, 2012 - Revision: 1