Is this issue fixed in any latest release of bonecp? We are using 0.8.0-RELEASE version with postgres 9.4.7 and connections get closed abruptly at random times. We use following config:
<property name="connectionTestStatement" value="SELECT NOW()" /> <property name="idleConnectionTestPeriodInMinutes" value="1" /> <property name="idleMaxAgeInMinutes" value="5" /> <property name="maxConnectionsPerPartition" value="20" /> <property name="minConnectionsPerPartition" value="1"/> <property name="poolAvailabilityThreshold" value="5"/> <property name="partitionCount" value="2" /> <property name="acquireIncrement" value="4" /> <property name="statementsCacheSize" value="50" />
Please note that we did not set maxConnectionAge or maxConnectionAgeInSeconds to 0 as I see from the source code that the default value is 0.
Please suggest if there is any workaround or a version in which this has been fixed.
Is this issue fixed in any latest release of bonecp? We are using 0.8.0-RELEASE version with postgres 9.4.7 and connections get closed abruptly at random times. We use following config:
<property name="connectio nTestStatement" value="SELECT NOW()" /> ctionTestPeriod InMinutes" value="1" /> eInMinutes" value="5" /> tionsPerPartiti on" value="20" /> tionsPerPartiti on" value="1"/> abilityThreshol d" value="5"/> Count" value="2" /> crement" value="4" /> sCacheSize" value="50" />
<property name="idleConne
<property name="idleMaxAg
<property name="maxConnec
<property name="minConnec
<property name="poolAvail
<property name="partition
<property name="acquireIn
<property name="statement
Please note that we did not set maxConnectionAge or maxConnectionAg eInSeconds to 0 as I see from the source code that the default value is 0.
Please suggest if there is any workaround or a version in which this has been fixed.