Just thinking about this some more.... So apparently, when I was using poolPreparedStatements="true", and I did conn.prepareStatement(SomeSQLString), I was getting back a Statement object created by DBCP to be pooled. When I called close() on that statement, it did not really close(), which was leaving lots of open cursors around.
Could maxOpenPreparedStatements possibly fix this? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
