[ https://issues.apache.org/jira/browse/GEODE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972043#comment-15972043 ]
ASF GitHub Bot commented on GEODE-2788: --------------------------------------- Github user masaki-yamakawa commented on the issue: https://github.com/apache/geode/pull/458 Thank you very much for your reply. > I'm uneasy about having this client-specific setting in the distributed system properties. These properties generally apply to DistributedSystem and its sub-components like DistributionManager and MembershipManager. I think so, too. Then, what do you think about the idea to add to the attribute of pool? For example, cache.xml like this: ` <pool name="MyPool" connect-timeout="15000"> <locator host="localhost" port="10334" /> </pool> ` API like this: ` ClientCacheFactory().addPoolLocator("localhost", 10334).setConnecTimeout(15000) ` * Default:59000 ms > Add official Socket timeout parameter when connecting to servers/locators > ------------------------------------------------------------------------- > > Key: GEODE-2788 > URL: https://issues.apache.org/jira/browse/GEODE-2788 > 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" in gemfire.properties. > 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. gemfire.properties:connect-timeout > 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 (v6.3.15#6346)