[
https://issues.apache.org/jira/browse/GEODE-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335821#comment-17335821
]
ASF subversion and git services commented on GEODE-9216:
--------------------------------------------------------
Commit ecda3f3a55e9ab9bfb3a042378361b08cce11416 in geode's branch
refs/heads/support/1.14 from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ecda3f3 ]
GEODE-9216 - User Guide: "gemfire.enableTcpKeepAlive" should be
"gemfire.setTcpKeepAlive" (#6400)
> 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
>
> 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)
