geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-2788) Add official Socket timeout parameter when connecting to servers/locators
Date Tue, 06 Jun 2017 05:09:18 GMT


ASF GitHub Bot commented on GEODE-2788:

Github user galen-pivotal commented on the issue:
    @masaki-yamakawa [Stack overflow](
suggests that you can trigger a build by closing and reopening the PR. I don't have write
access, so I can't kick it myself. Sorry for the slow response.

> Add official Socket timeout parameter when connecting to servers/locators
> -------------------------------------------------------------------------
>                 Key: GEODE-2788
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server, docs
>            Reporter: Masaki Yamakawa
>            Priority: Minor
>              Labels: patch
> When connecting from the client to the servers/locators, if the servers/locators is not
started, the connection can not be established and a Socket timeout occurs.
> This timeout value is 59 seconds by default. This timeout value is too long. This timeout
value can be changed by specifying the unofficial parameter "gemfire.PoolImpl.HANDSHAKE_TIMEOUT"
in java system property, but I corresponded so that it can be specified by official parameters.
> Like the NativeClient, the official parameters should be specified by "connect-timeout"
> Timeout values ​​are determined in the following order of priority.
> 1. java system property:gemfire.PoolImpl.HANDSHAKE_TIMEOUT
> 2. java system property:gemfire.connect-timeout
> 3.
> 4. default:59000 milli seconds
> As another idea, there is also an idea to make it possible to specify it as an attribute
of Pool. In that case NativeClient needs the same modification.

This message was sent by Atlassian JIRA

View raw message