The simple answer is that the code is attempting to do a commit on the underlying
datasource in the wrong context. Again, the easiest thing for you to do is to use the
<no-tx-datasource> and control the autocommit value yourself programmatically at
runtime.
Chances are Sun Application Server via a service specific deployment descriptor or the
runtime environment is managing this setting somehow for your deployment. This effecitvely
(again, my best guess) amounts to a proprietary feature that does not integrate with
JBoss.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016638#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...