Right now our DBCPDriverDataSource by default sets the maxIdle to 1.
This is not wrong but also not really good in terms of performance.
It is usually much better to keep it at a much higher number. Usually somewhere around maxActive, except when maxActive is really high.
So I'd rather keep it at 10 or even at maxActive if this param is set.
If the connections are not used, then they will get unlocked after some time anyway.
But keeping the number 1 for maxIdle basically disables the pool, which is not wise.