You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bill Burcham (Jira)" <ji...@apache.org> on 2021/02/03 00:00:00 UTC
[jira] [Updated] (GEODE-8796) missing doc for: gfsh start server
with --max-threads > 0 being incompatible with SSL
[ https://issues.apache.org/jira/browse/GEODE-8796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Burcham updated GEODE-8796:
--------------------------------
Summary: missing doc for: gfsh start server with --max-threads > 0 being incompatible with SSL (was: missing doc for: gfsh start server with --max-threads > 0 being incompatible with SSl)
> missing doc for: gfsh start server with --max-threads > 0 being incompatible with SSL
> -------------------------------------------------------------------------------------
>
> Key: GEODE-8796
> URL: https://issues.apache.org/jira/browse/GEODE-8796
> Project: Geode
> Issue Type: Bug
> Components: docs
> Affects Versions: 1.12.0, 1.13.1, 1.14.0
> Reporter: Bill Burcham
> Assignee: Bill Burcham
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.1, 1.13.2, 1.14.0
>
>
> When SSL is configured, setting a --max-threads parameter value greater-than zero, for the gfsh start server command, always results in an exception with a message like this:
> Caused by: java.lang.IllegalArgumentException: Selector thread pooling can not be used with client/server SSL. The selector can be disabled by setting max-threads=0.
> When this ticket is complete, the documentation for the --max-threads parameter, on the gfsh start server documentation page, will stipulate that setting this value to a non-default value is not supported when SSL is configured for client-server communication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)