I already got a response to the ehancement request. Apparently the documentation will be changed to this:
Make sure your connection has some resources left for the other statements. Pooling PreparedStatements may keep their cursors open in the database, causing a connection to run out of cursors, especially if maxOpenPreparedStatements is left at the default (unlimited) and an application opens a large number of different PreparedStatements per connection. To avoid this problem, maxOpenPreparedStatements should be set to a value less than the maximum number of cursors that can be open on a Connection. Looks good to me. Not sure if it will have to wait for 1.3 or if they will work it into the current documentation after some review. Bill Davidson wrote:
Christopher Schultz wrote: >I see you've cross-posted to commons-user. That's good, but you probably >want to file an actually bug report / enhancement request for the >documentation. Filed. Key: DBCP-301
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
