</snip> As a further test I just took out my explicit rollback in my DAOFactory close() method, and swapped back to commons dbcp. Added an update that wasn't explicitly committed, and it correctly did not get committed when the connection was closed. Swapped back to tomcat dbcp and repeated, it got committed without an explicit commit statement.
I'm really puzzled as to why *I* have to explicitly rollback on close if autocommit is not enabled, instead of tomcat dbcp handling that when commons dbcp appears to do it. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
