You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I saw that you marked this as an Enhancement. Does it mean that you agree that adding a socket connect timeout configuration property is a good idea?
Until the enhancement is implemented, is there a workaround?
Hi,
Even though method tryToConnect in SocketConnector.java (see https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/nio/tcp/SocketConnector.java) takes a connection timeout parameter as input, that parameter is hard-coded to 0 - i.e., use OS default timeout - for IPv4 addresses and to 3,000 milliseconds for IPv6 addresses.
Therefore, there is currently no way to change the socket connect timeout via a configuration property.
Is this by design?
Thanks.
The text was updated successfully, but these errors were encountered: