My concern is you are proposing to change the behavior of an existing geode
feature. I think 0 is currently supported for both these properties in the Java
client. I would think they cause immediate idle expiration and a very hot load
conditioning. Your proposal would make 0 mean something very
Hi,
According to the documentation of the Geode Java client API, setting -1 for
idleTimeout in a Pool indicates that connections should never expire:
https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setIdleTimeout-long-
Nevertheless, according to th
