I've figured out the problem. The Driver had a built in Datasource which was doing its own pooling management, hence keeping connections open even though the tomcat-pool saw them as closed. In effect I had a datasource pool within a datasource. Removing the connection attribute solved the problem.
Regards Kiren -- View this message in context: http://tomcat.10.x6.nabble.com/Fwd-Tomcat-Jdbc-Pool-NumActive-vs-actual-Established-Connections-tp4997798p4997849.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
