[ http://jira.jboss.com/jira/browse/JBTM-98?page=all ] Mark Little updated JBTM-98: ---------------------------- Fix Version/s: 4.4 (was: 4.2.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBTM-98?page=comments#action_12343650 ] Jonathan Halliday commented on JBTM-98: --------------------------------------- Per above forum reference, issue was reported as problem with Xid length when using Oracle 10g OCI JDBC driver, with suggested fix: "The driver does not like the global and branch qualifier IDs if they are not padded to 64 bytes. I have modified the methods XidImple.getGlobalTransactionId() and XidImple.getBranchQualifier() to return a padded array of 64 bytes." Attempted to reproduce the issue using Oracle 10g release 2 on linux for both client and server. Unable to reproduce issue, XA transaction worked ok. Oracle may have fixed issue in their driver by 10g, so I also attempted to reproduce the issue using Oracle 9i release 2 client/server on linux. Still worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBTM-98?page=comments#action_12343778 ] Moises Quinto commented on JBTM-98: ----------------------------------- what is the setup of your test? If I have a single JBoss server talking to oracle then it works fine. When I try the following scenario is when I get the problem (both server 4.0.3 SP1 and JBossts 4.2): Server1 : starts the global distributed transaction, performs local oracle database operations and calls a server2Bean on server2 // this method has the tx "required" attribute in ejb-jar.xml performGlobalTx(){ doSomething(); // do oracle operations server2Bean.doSomething(); // call remote jboss Server2 } Server2: the bean on this server updates the same oracle database: doSomething(){ performDBOperations...; // here is where I get the exceptions reported in the forum <<<<--------------------here } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBTM-98?page=all ] Mark Little closed JBTM-98. --------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira