This bug applies to the code currently in CVS, and goes back to at least v0.9.8:
In the method RelationalDatabaseSessionFactory.openSession(Connection conn, boolean autoClose, long timestamp), the autoClose and autoCommit arguments being passed to the RelationalDatabaseSession constructor are the wrong way around, and need to be swapped. The symptom, in my case, was that I was supplying an external connection to openSession, but Hibernate was returning null from Session.close(), instead of the external connection. In addition, it was apparently retaining the connection for its pool (in DriverManagerConnectionProvider.closeConnection). This meant that connections from my servlet engine's pool (Resin) were being drained into Hibernate's pool, eventually causing Resin to go into a serious sulk when it found that its swimming privileges had been revoked. :) I imagine this may be causing other symptoms related to autoCommit. Calling openSession with no arguments would set autoCommit to true, and calling it with a connection would set it to false. Anton _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
