In README.md we have table with description of ConnectionPoolConfiguration options.
maxLifeTime
maxAcquireTime
maxCreateConnectionTime
Has such phrase in description: Negative values indicate no timeout
At the same time
ConnectionPoolConfiguration.Builder has checks for that values and they could not be null, or negative
Ex:
public ConnectionPoolConfiguration.Builder maxIdleTime(Duration maxIdleTime) {
Assert.requireNonNull(maxIdleTime, "maxIdleTime must not be null");
if (maxIdleTime.isNegative()) {
throw new IllegalArgumentException("maxIdleTime must not be negative");
} else {
// . . .
Do we need to correct they to Zero (PT0S) values indicate no timeout ?
What you see is a difference between 0.8.x (0.8.x branch) and 0.9.x (main branch). We changed the no timeout/zero-timeout behavior with #77 for the 0.9.x development line.
In README.md we have table with description of ConnectionPoolConfiguration options.
Has such phrase in description:
Negative values indicate no timeout
At the same time ConnectionPoolConfiguration.Builder has checks for that values and they could not be null, or negative Ex:
Do we need to correct they to
Zero (PT0S) values indicate no timeout
?