This is an important issue. We also have to patch jboss 4.0.3 by hand to alter this Hibernate property.
I don't understand how can this be an immutable default: it returns the jdbc connections to the pool without considering a possible running transaction? I may not see everything, but it was also leaking the jdbc connections for us. I've checked the close calls to the hibernate session, and to the jdbc connections, and both was correct, and still I ended up with a full jdbc pool. Turning off the aggressive release (with the patch) solved all our issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902258#3902258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3902258 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
