From: Mark R. <ma...@la...> - 2013-04-25 08:28:28
|
On Thu, 25 Apr 2013 10:16:33 +0200, Jiri Cincura <di...@ci...> wrote: > How I'm thinking. The connections are normally in pool, when you're > using some, it's not in pool (actually it's still in the pool's > collection, but "marked as used") logically. When you're cleaning all > pools you are cleaning connections that are pooled (in pool). Hence > connections not in pool should be untouched. At least that's what I > think. On the other hand, this a huge breaking change. Not sure it's > worth changing it. :\ > > Also thinking from the other hand. If you have reference to some > connection that's used and you'd like to close and clear all, why not > to first close connections you're holding and then clean pools. Right? > What's to reason to have method that would do it under your hands... You could also see it from a different point: some part of your code is misbehaving (ie not releasing connections back to the pool in a timely fashion), being able to force all connections from the pool to close might be a great way to detect (or mitigate) this problem. Mark |