[ 
https://issues.apache.org/jira/browse/GEODE-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157743#comment-17157743
 ] 

ASF GitHub Bot commented on GEODE-8349:
---------------------------------------

lgtm-com[bot] commented on pull request #5363:
URL: https://github.com/apache/geode/pull/5363#issuecomment-658455639


   This pull request **introduces 1 alert** and **fixes 1** when merging 
ced3c7a3fc32cfa1ba209215d0105a43a0246161 into 
1ebd307ae1ae87c53f0ff6b8f0c83ab2feda93cd - [view on 
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-5ee74036f8700de46d755c33bc1a74a1d0d44345)
   
   **new alerts:**
   
   * 1 for Potential input resource leak
   
   **fixed alerts:**
   
   * 1 for Potential input resource leak


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> reinstate use of SSLSocket for cluster communication
> ----------------------------------------------------
>
>                 Key: GEODE-8349
>                 URL: https://issues.apache.org/jira/browse/GEODE-8349
>             Project: Geode
>          Issue Type: Bug
>          Components: membership, messaging
>            Reporter: Bruce J Schuchardt
>            Assignee: Bruce J Schuchardt
>            Priority: Major
>
> We've found problems with "new IO"'s SSLEngine with respect to support for 
> TLSV1.  We've also seen anomalous performance using that secure 
> communications mechanism.  The introduction of the use of the "new IO" 
> SSLEngine was originally to 1) reduce code complexity in the 
> org.apache.geode.internal.tcp package and 2) to set the stage for its use in 
> client/server communications so that selectors could be used in c/s 
> communications.
> This ticket aims to reintroduce the use of SSLSocket in cluster 
> communications without restoring the old, poorly tested SSL code paths.  The 
> new implementation should have as good or better performance than the 
> previous"old IO" implementation and the more recent "new IO" SSLEngine 
> implementation as well.  This should be apparent in the CI benchmark jobs.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to