You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/29 19:46:00 UTC
[jira] [Updated] (GEODE-6150) Allow use of client/server
max-threads with SSL
[ https://issues.apache.org/jira/browse/GEODE-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated GEODE-6150:
----------------------------------
Labels: SmallFeature pull-request-available (was: SmallFeature)
> 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)