PoolWatchThread does not respect a minConnectionsPerPartition=0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BoneCP |
New
|
Undecided
|
Wallace Wadge |
Bug Description
Hello,
We are currently using 0.8.0 with the following configuration:
bonecp.
bonecp.
bonecp.
bonecp.
bonecp.
bonecp.
bonecp.
bonecp.
bonecp.
We have been noticing that the minimum is not respected. Actually the "PoolWatchThread" always opens up a new connection when the available are 0. During debugging of that class and where there is NO OTHER db activity via our app, here is what we get: When the debugger has reached line 82 of PoolWatchThread
this.partition.
this.partition.
this.partition.
maxNewConnections = 50
{code}
maxNewConne
// loop for spurious interrupt
while (maxNewConnections == 0 || (this.partition
if (maxNewConnections == 0){
this.
}
this.
maxNewConn
}
if (maxNewConnections > 0
&& !this.pool.
line 82 ---> fillConnections
// for the case where we have killed off all our connections due to network/db error
if (this.partition
fillConne
}
}
{code}
That means the "Math.min(
I believe that the behavior above should be okay if we had minConnectionsP
Is this a bug or are we missing something?
It looks to me that somehow the "this.partition .getMinConnecti ons()" should be a part of the condition of the "while" clause.