Tomcat provides the removeAbandoned and removeAbandonedTimeout parameters when setting up data sources in server.xml. But according to the documentation I've read, abandoned connections only get closed and recycled when available connections run low and new connections are requested.
Is there a way for me to forcibly close/release abandoned connections on the server from a privileged application running on the same server? BTW, I'm running Tomcat 5.5 on a Windows 2003 box, running against DB2 on an iSeries box (jt400 for the JDBC driver), using Tomcat's DBCP for the pooling. Thanks, David --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
