[
https://issues.apache.org/jira/browse/GEODE-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482139#comment-17482139
]
ASF subversion and git services commented on GEODE-9973:
--------------------------------------------------------
Commit a4c4f75116f0b9cae9c4c14e0bcb6ce1d15f134e in geode's branch
refs/heads/revert-7294-feature/GEODE-9973-socket-lease-time-docs from Dave
Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a4c4f75 ]
Revert "GEODE-9973: Correct docs regarding P2P socket timeout behaviour (#7294)"
This reverts commit 763f590fe1e9a62ec21eae3a8c0cf0de2fee8594.
> Documentation: socket-lease-time is not used to return sockets to a pool but
> to close them
> ------------------------------------------------------------------------------------------
>
> Key: GEODE-9973
> URL: https://issues.apache.org/jira/browse/GEODE-9973
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Alberto Gomez
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The "Making sure you have enough sockets" Geode documentation section says
> the following about socket-lease-time (check underlined sentence):
>
> Peer-to-peer. For peer-to-peer threads that do not share sockets, you can use
> the socket-lease-time to make sure that no socket sits idle for too long.
> +When a socket that belongs to an individual thread remains unused for this
> time period, the system automatically returns it to the pool.+ The next time
> the thread needs a socket, it creates a new socket.
>
> Actually, the system automatically closes the connection in the situation
> described instead of returning it to any pool.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
