James House wrote: > A few months back I made my own hacks to > DBCP in order to have it find places in > our code that didn't free up DB resources > properly. > > I was able to generate class names and > line-numbers (stack trace) for every place > in the code that a statement or result set > was created but never closed, and also able > to track where connections were borrowed > and never returned.
> If anyone's interested, I could try > digging it up, and posting it. Sounds great, especially if we can do it relatively unobtrusively (or optionally). By all means, put together a patch.
