Bill Davidson wrote:
>Could maxOpenPreparedStatements possibly fix this?
Apparently it does.
The DBCP config docs need a better warning on poolPreparedStatements:
"*NOTE* - Make sure your connection has some resources left for the
other statements."
just doesn't quite cut it. Something more like:
"Pooling PreparedStatement's may keep their cursors open in the database,
causing you to run out of cursors. You should also set
maxOpenPreparedStatements to some value less than the maximum number
of cursors you can have on a Connection."
or something along those lines.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
