GitHub user masaki-yamakawa opened a pull request:

    https://github.com/apache/geode/pull/474
    GEODE-2788: Add official Socket timeout parameter when connecting to 
servers/locators

    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.
    The official parameters are specified by the attribute of 
Pool.(default:59000 ms)
    
    For example, cache.xml like this:
    ```xml
    <pool name="MyPool" socket-connect-timeout="15000">
      <locator host="localhost" port="10334" />
    </pool>
    ```
    
    API like this:
    ```java
    ClientCacheFactory().addPoolLocator("localhost", 
10334).setPoolSocketConnecTimeout(15000);
    ```
     or
    ```java
    PoolManager.createFactory().addServer("localhost", 
40404).setSocketConnectTimeout(15000);
    ```

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/masaki-yamakawa/geode feature/GEODE-2788

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/474.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #474
    
----
commit acd97c76a1e8f4690e8cd1050941c16e8f869502
Author: masaki.yamakawa <masaki.yamak...@ulsystems.co.jp>
Date:   2017-04-22T15:44:08Z

    GEODE-2788: Add official Socket timeout parameter when connecting to 
servers/locators
    
    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.
    The official parameters are specified by the attribute of 
Pool.(default:59000 ms)
    
    For example, cache.xml like this:
    <pool name="MyPool" socket-connect-timeout="15000">
      <locator host="localhost" port="10334" />
    </pool>
    
    API like this:
    ClientCacheFactory().addPoolLocator("localhost", 
10334).setPoolSocketConnecTimeout(15000);
     or
    PoolManager.createFactory().addServer("localhost", 
40404).setSocketConnectTimeout(15000);

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to