[
https://issues.apache.org/jira/browse/GEODE-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285248#comment-17285248
]
ASF GitHub Bot commented on GEODE-6150:
---------------------------------------
lgtm-com[bot] commented on pull request #5270:
URL: https://github.com/apache/geode/pull/5270#issuecomment-779888021
This pull request **fixes 2 alerts** when merging
6339caeb6c8ce2307cb9b08707299fd34df9a5d0 into
ea37a2d31e023aa5645c6404d1d55191e689b926 - [view on
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-f9de1a3759e35d42ef8a39786d7d2d488d5ac10f)
**fixed alerts:**
* 2 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
> Allow use of client/server max-threads with SSL
> -----------------------------------------------
>
> Key: GEODE-6150
> URL: https://issues.apache.org/jira/browse/GEODE-6150
> Project: Geode
> Issue Type: New Feature
> Components: client/server
> Reporter: Bruce J Schuchardt
> Assignee: Mario Ivanac
> Priority: Major
> Labels: SmallFeature, pull-request-available
>
> Cache servers have a max-threads setting that causes the server to limit the
> number of threads used by clients. The implementation uses Java new I/O
> though and that doesn't currently play well with SSL/TLS secure
> communications. If you attempt to configure the server to use secure
> communications _and_ max-threads it throws an IllegalArgumentException with
> the message
> Selector thread pooling can not be used with client/server SSL. The selector
> can be disabled by setting max-threads=0.
> The server code should be modified to use the JDK's SSLEngine to implement
> SSL/TLS over NIO and get rid of this restriction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
