|
Problem IT38963
|
Status: Closed |
CONNECTING JAVA PROGRAM VIA SSL CAN FAIL WITH "SSLHANDSHAKEEXCEPTION: NO APPROPRIATE PROTOCOL"
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
connecting a java program via SSL can fail with:
java.sql.SQLException: Socket connection to server
(user@machine:12345) failed. Check your server is reachable from
this client on the host:port specified.
at
com.informix.jdbc.IfxSqliConnect.(IfxSqliConnect.java:1536
)
at
com.informix.jdbc.IfxDriver.connect(IfxDriver.java:167)
Caused by: javax.net.ssl.SSLHandshakeException: No appropriate
protocol (protocol is disabled or cipher suites are
inappropriate)
Error in the online.log
07:27:21 listener-thread: err = -28014: oserr = 0: errstr =
from machine to server serv1 cannot initialize GSKit secure
socket/GSK_ERROR_IO (GSKit:406): Secure Sockets Layer error:
from machine to server serv1 cannot initialize GSKit secure
socket/GSK_ERROR_IO (GSKit:406). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix JDBC prior to 4.50.JC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix JDBC 4.50.JC8. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix JDBC prior to 4.50.JC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix JDBC 4.50.JC8. *
**************************************************************** |
| Comment |
Fixed in Informix JDBC 4.50.JC8. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2021
05.04.2022
05.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
