Re: JONAS JOTM - SubCoordinator.doCommit : Got XAException fromres.commit: Cannot send res.commit:javax.transaction.xa.XAException (error code = -3) --null

"Guillaume Sauthier (OW2)" <[email protected]> Wed, 6 Jul 2011 23:57:30 +0200
Newsgroups gmane.comp.java.objectweb.jonas
Message-ID <CAG1yf3OkDgihUvZg2a-zDFNVA7gwO7qCSiCrmj05szLy+G+oDA@mail.gmail.com>
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 <[email protected]>

> 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.
>