geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vahram Aharonyan (JIRA)" <>
Subject [jira] [Updated] (GEODE-3563) SSL socket handling problems in TCPConduit run
Date Mon, 18 Sep 2017 09:01:00 GMT


Vahram Aharonyan updated GEODE-3563:
         Priority: Critical  (was: Major)
    Fix Version/s:     (was: 1.2.1)

> SSL socket handling problems in TCPConduit run
> ----------------------------------------------
>                 Key: GEODE-3563
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Vahram Aharonyan
>            Priority: Critical
>             Fix For: 1.3.0
> Here are two cases that seems to problematic in flow:
> 1. has no action performed for the case when SSLException is thrown
from sslSocket.startHandshake(), as a result the socket remains open. 
> Catch block from the end of  configureServerSSLSocket() will just report a fatal error(even
it seem that this portion is going to be removed in 1.2.1 according to GEODE-3393) and re-throw
the exception.
> 2. configureServerSSLSocket call is performed without setting socket timeout before that.
This can bring to run thread blocking case if read initiated from the SSL handshake flow will
not return. Linking to similar issues observed with other acceptors previously: GEODE-2898,

This message was sent by Atlassian JIRA

View raw message