Feedback
Did this article resolve your question/issue?

   

Article

IllegalArgumentException occurs when connecting to Salesforce with JRE 1.8

Information

 
TitleIllegalArgumentException occurs when connecting to Salesforce with JRE 1.8
URL NameIllegalArgumentException-occurs-when-connecting-to-Salesforce-with-JRE-1-8
Article Number000184845
EnvironmentProduct: Connect for ODBC Salesforce driver
Version: All supported versions
OS: All supported platforms
Database: Salesforce
Application: All supported applications
Question/Problem Description
IllegalArgumentException occurs when connecting to Salesforce with JRE 1.8 while using the Connect for ODBC Salesforce driver.
Steps to Reproduce
Clarifying Information
Problem only occurs with JRE 1.8
Data source contaqins the entry JVMArgs=-Dhttps.protocols="TLSv1.1,TLSv1.2" 
Error Message[DataDirect][ODBC 20101 driver][20101]java.lang.IllegalArgumentException: IllegalArgumentException invoking xxxxxxxx: "TLSv1.1
Defect Number
Enhancement Number
Cause
The Connect for ODBC Salesforce driver version  5.1.4.000143 and above do not use the -Dhttps.protocols connection argument.
Resolution
Remove the entry for -Dhttps.protocols parameter. The driver will automatically negotiate the best TSL setting. JDK 1.8 uses TLSv1.2 by default, but supports SSLv3, TLSv1, TLSv1.1 and TLSv1.2
 
Workaround
Notes
Last Modified Date5/31/2017 6:43 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.