You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dave Barnes (Jira)" <ji...@apache.org> on 2021/04/29 22:12:00 UTC
[jira] [Resolved] (GEODE-9216) User Guide -
"gemfire.enableTcpKeepAlive" should be "gemfire.setTcpKeepAlive"
[ https://issues.apache.org/jira/browse/GEODE-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Barnes resolved GEODE-9216.
--------------------------------
Fix Version/s: 1.12.2
1.13.2
1.15.0
1.14.0
Resolution: Fixed
> User Guide - "gemfire.enableTcpKeepAlive" should be "gemfire.setTcpKeepAlive"
> -----------------------------------------------------------------------------
>
> Key: GEODE-9216
> URL: https://issues.apache.org/jira/browse/GEODE-9216
> Project: Geode
> Issue Type: Bug
> Components: docs
> Affects Versions: 1.13.2
> Reporter: Dave Barnes
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0, 1.13.2, 1.12.2
>
>
> This keep alive parameter was documented as "gemfire.enableTcpKeepAlive". But actually this parameter `gemfire.setTcpKeepAlive`.
> https://geode.apache.org/docs/guide/113/managing/monitor_tune/socket_tcp_keepalive.html
> This bug has been in place since Geode 1.0 – Fix should include back-ports to at least some of the recent versions.
> Citation above may be the only occurrence. Fix should include searching for other occurrences.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)