It says you are trying to control the transaction when you should be using XA.
Do you have no-tx-separate-pools configured? If not add it. The option didn't exist in 3.2.1 Oracle XA is notoriously broken, we have at least four different configurations to workaround/fix it: 1) xid pad=true in conf/jboss-service.xml (it doesn't like the short versions) 2) sameRM = false (this is just broken) 3) track-connection-by-tx (it doesn't like efficient pooling - no interleaving) 4) no-tx-separate-pools (it doesn't like using an xa connection outside a transaction after it has been used in a transaction and vice-versa) You should also enable track-statements, which will reveal where you are not closing statements and hence result sets. There are some subtle rules about when autocommit transactions end if you don't do this. If you have the option to use java 1.4 I would recommend it over java 1.3 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835308#3835308 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835308 ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
