i'm successfully using commons jakarta dbcp connection pooling in all of my projects (with tomcat). i've seen that in the latest dbcp 1.2 edition the whole abandoned connections tracking was depricated. i googled this and found out that some folks stopped to use abandoned connections tracking in production (by removing removeAbandoned - true in server.xml) and some other folks keep it. i didn't really find any info about the problem itself, but as you understand it bothers me.
do you know anything about it?
Arthur, where are your pants? Check under this tiny ad.