Yes A and B use JONAS.
The exception comes from A but i have to check again if an exception is logged in B.
I tried to use debug mode with JOTM code and i noticed that there are as many commits as burlap requests instead of only one because the purpose is to have one Java transaction in A with several requests to B (begin transaction - burlap req1...burlap req n - end transaction).
With debug mode i think that JOTM considers that there are different datasources so it tried to do as many commits as datasources but in fact i want to do a Java transaction not a JDBC transaction in A.
Message du 08/07/11 21:06
De : "Guillaume Sauthier (OW2)"
Objet : [jonas] Re: Re: Re: JONAS JOTM - SubCoordinator.doCommit : GotXAException fromres.commit: Cannot send res.commit:javax.transaction.xa.XAException (error code = -3) --null
I don't know tyrex, so I can only help with JOTM ...
So far, what I understand is that your have 2 applications: A and B
B is connected to the database and performs its own commits.
A communicate with B using burlap protocol, so there is no Transaction
propagation between A and B.
That means that transactions on B are completely independent of transactions
on A.
That also means that if no exceptions is thrown from B when something is
going wrong, therer will be not automatic rollback of the transaction(s) on
A.
Concerning the JOTM configuration on JOnAS, there are a few things you can
* change timeout (default to 60s)
* something about using a remote TM instead of a local one
BTW, A and B are both running JOnAS ?
The exceptions comes from B, right ?
--G
2011/7/7 payne.max
Post by payne.maxNo 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)"
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,
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.