[ https://issues.apache.org/jira/browse/IGNITE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216951#comment-16216951 ]
Alexey Popov commented on IGNITE-6690: -------------------------------------- https://github.com/apache/ignite/pull/2917 The fix is ready. 1. It includes changes in ServerImpl and ClientImpl of SpiDiscovery with StreamCorruptedException 2. Unit tests are added 3. The special case when non-SSL client/server connects to SSL-enabled server is handled as before. It is done by looking at StreamCorruptedException message to check for SSL Alarm message pattern > DiscoverySpi: Clientmode Ignite should not fail on handshake errors > ------------------------------------------------------------------- > > Key: IGNITE-6690 > URL: https://issues.apache.org/jira/browse/IGNITE-6690 > Project: Ignite > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: general > Affects Versions: 2.2 > Reporter: Alexey Popov > Assignee: Alexey Popov > Labels: discovery > Fix For: 2.4 > > > Ignite in Client mode should not fail on handshake unmarshalling errors. It > should go to the next IP/port from ipFinder list > http://apache-ignite-developers.2346864.n4.nabble.com/DiscoverySpi-Handshake-unmarshalling-errors-at-Client-client-mode-td23467.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)