Last week I committed some changes to DBCP that made sure that all ResultSet's and Statement's were closed on a Connection close.
You might try the latest nightly build or build from CVS. Regards, Glenn Bill Schneider wrote: > > I've been using the dbcp BasicDataSourceFactory with Tomcat, as a > replacement for Tyrex brokenness. I ran into some trouble with it under > heavy load: after running it for a while I end up with an Oracle "too many > open cursors error". > > The problem is a combination of dbcp code and application code. The > application code was written with the (possibly incorrect) assumption that > calling conn.close() resets the connection, closing any associated > statements, such that the connection is good-as-new if it's recycled and > reassigned. > > This worked fine until bringing in DBCP, because the statements are > > to being able to call conn.close(), > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- ---------------------------------------------------------------------- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder | MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | ---------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
