[
https://issues.apache.org/jira/browse/GEODE-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219934#comment-17219934
]
ASF GitHub Bot commented on GEODE-6150:
---------------------------------------
lgtm-com[bot] commented on pull request #5270:
URL: https://github.com/apache/geode/pull/5270#issuecomment-715586038
This pull request **introduces 10 alerts** and **fixes 2** when merging
0d64a52b557f693d2efeb32183e6250e884abdf5 into
0fdfc1ad1e272eed9bf5e2ee59816b75b262d9c6 - [view on
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-370dabfbf4f68f1f62b81c97f126c51f64625bd7)
**new alerts:**
* 4 for Potential output resource leak
* 4 for Dereferenced variable may be null
* 2 for Potential input resource leak
**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)
