Actually, the real issue is that JBoss's jdbc resource adapter keeps track of the auto-commit state itself so it can optimize its usage: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJCALazyAutoCommit
Part of that, is the assumption that all connections are in getAutoCommit()==true state when they are created (as per spec). Support for this anti-spec behaviour would require the JBoss JDBC resource adapter to do a getAutoCommit() on every new connection rather than assuming a value of true. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021066#4021066 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021066 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user