On 15/12/2009 17:34, Guillermo Fernandes wrote: > Hi, > > I'm using ddlutils 1.0 and tomcat jdbc pool 1.0.7.1 and I getting an error > due to a connection is closed and the pool is not aware of that. > Basically the issue is that ddlutils has a resultset iterator and when it > finishes it closes the connection by getting it from the * > resultSet.preparedStatement.connection* and the connection returned is not > the proxy that the pool has created. > > So the issue happens when another client retrieves a connection from the > pool because the pool returns a connection that was actually closed. > Why tomcat jdbc pool is not creating proxies for preparedStatements and > resultSets like commons-dbcp?
That would be a bug. Please create a bugzilla entry. > Is there any other way to address this issue? Use DBCP or one of the other connection pools? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
