geode-dev 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 Thu, 11 May 2017 15:45:04 GMT


ASF GitHub Bot commented on GEODE-2788:

Github user bschuchardt commented on the issue:
    There is another failure in AnalyzeSerializablesJUnitTest caused by this change.  Certain
tests serilalize/deserialize PoolAttributes, so this class is DataSerializable.  This PR changes
the serialized form of the class, so the sanctionedSerializables.txt file must be updated
to reflect that this change is acceptable:
    org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTest > testDataSerializables
        java.lang.AssertionError: Modified classes--------------------------------------------
        :  toData (len=153,expected=145), and fromData (len=153,expected=145)
        If the class is not persisted or sent over the wire add it to the excludedClasses.txt
file in the 
        org/apache/geode/codeAnalysis directory.  Otherwise if this doesn't 
        break backward compatibility move the file actualDataSerializables.dat to the codeAnalysis

        test directory and rename to sanctionedDataSerializables.txt
            at org.apache.geode.codeAnalysis.AnalyzeSerializablesJUnitTest.testDataSerializables(

> 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