Pivotal Knowledge Base


Connection Pool read-timeout and retry-attempts

Applies to

All versions of GemFire


Pool properties read-timeout and retry-attempts are not applicable to locator connections.


The GemFire client-pool connection properties 'read-timeout' and 'retry-attempts' are only applicable when a client is connected to a server and are not applicable to locator connections. Hence, if locator is not available, a client will throw a LocatorNotAvailable exception and there is no way to retry on locator. 

Additionally, when a locator is removed from the locator list due to unexpected exception retry attemps will not work.


Powered by Zendesk