I have found that adding <track-connection-by-tx>true</track-connection-by-tx> to my datasource definition has fixed this problem in both JBoss 3.2.6 and JBoss 3.2.5.
It's a bit frustrating as I have no idea why and only stumbled on the solution due to similar problems I had using JBoss 4.0. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853640#3853640 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853640 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
