[ https://issues.apache.org/jira/browse/IGNITE-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454377#comment-16454377 ]
Igor Sapego commented on IGNITE-8394: ------------------------------------- The issue was that when using asynchronous connection it is preferred to use {{SSL_connect}} instead of \{{BIO_do_connect}}. Also, it is needed to check return of the {{SSL_get_error_}} after connect for {{SSL_ERROR_WANT_WRITE}}, {{SSL_ERROR_WANT_READ}} and {{SSL_ERROR_WANT_CONNECT}} values, as they are not errors, but instructions on the next connection step. Weirdly enough, reproduced only on the remote host (maybe because of the longer network delay). > ODBC: Can not establish SSL connection to remote host. > ------------------------------------------------------ > > Key: IGNITE-8394 > URL: https://issues.apache.org/jira/browse/IGNITE-8394 > Project: Ignite > Issue Type: Bug > Components: odbc > Affects Versions: 2.4 > Reporter: Igor Sapego > Assignee: Igor Sapego > Priority: Major > Labels: odbc, ssl, tls > Fix For: 2.6 > > > Driver connects to the local server, but when connecting to remote server > client sometimes returns error when trying to establish async connection, > though the connection established successfully, if the error is ignored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)