Re: Re: JONAS JOTM - SubCoordinator.doCommit : Got XAException fromres.commit: Cannot send res.commit:javax.transaction.xa.XAException (error code = -3) --null
"payne.max" <[email protected]> Thu, 07 Jul 2011 12:04:32 +0100
| Newsgroups | gmane.comp.java.objectweb.jonas |
|---|---|
| Message-ID | <1828491.69386.1310033072307.JavaMail.www@wwinf8201> |
No multiple commits noticed when i used Tyrex with JONAS or Websphere transaction manager with Websphere application server. The only problem i had with Tyrex is a random error (java.lang.IllegalStateException: Cannot resume, current thread already associated with a transaction) so i would like to test with JOTM and it seems the behaviour is different as with the same code there are several commits inside the same transaction. On the application B i have no problem to use it: web application connected to Oracle database server so the transactions are managed successfully (begin/commit at least). Unfortunately i don't know excatly the kind of transactions as B is proprietary software and A is based on API of B. I did not find a clear documentation to understand how to use and configure JOTM with JONAS. > Message du 06/07/11 23:57 > De : "Guillaume Sauthier (OW2)" > A : [email protected] > Copie à : > Objet : [jonas] Re: JONAS JOTM - SubCoordinator.doCommit : Got XAException fromres.commit: Cannot send res.commit:javax.transaction.xa.XAException (error code = -3) --null > > As you don't use RMI communication layer between A and B, I can't see how the transactions could be propagated. > So as a JOTM point of view, there is only 1 transaction on A. > > Do you also manage transactions (begin/commit/rollback) on B ? > If so, what kind ? Required/RequiresNew/Never, ... ? > > --G > > 2011/7/6 > Hello, > > I have the following issue with JONAS included in JONAS 4.8.7: > > SubCoordinator.doCommit : Got XAException from res.commit: Cannot send > res.commit:javax.transaction.xa.XAException (error code = -3) --null > > The error occured in a web application A which sends requests to other > application B which is connected to Oracle database server. > The communication between two applications is done by burlap protocol. > Several burlap calls from A are wrapped inside the same transaction (begin > transaction - several burlap calls - end transaction). > The problem is that there are as many commits as burlap requests, the first > commit does not cause any issue but others cause transaction not found issue. > Is there any configuration to do in JONAS or JOTM? > > Could you help me please. > > Thank you. > > Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net