fyi, we ended up using 4.0.3SP1 with patching jboss-hibernate.jar to use AFTER_TRANSACTION.
using hibernate from the web layer (self started JTA transaction) with AFTER_STATEMENT jboss was leaking the actual oracle connections (no resource in pool exception after a few operations) using hibernate from CMT beans with pristine jboss works fine! patching jboss to use hibernate with AFTER_TRANSACTION works both for CMT beans and user started JTA transactions. ps: warning, it all happened several days ago in a many hours long debug session. my memory _may_ trick me... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907615#3907615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907615 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
