Dasarath Weeratunge schrieb:
Quoting Dominik Heller <[EMAIL PROTECTED]>:
What does it report as the status of transaction at the point of timeout?
We keep the Coordinator objects even after transaction completion in order to
respond to any stray messages that may arrive later. However, I'm not sure
whether this is indeed the case.
-- Dasarath
Hi Hannes,
first of all THX so much it's almost working now. The only problem occuring
now is a timeoutException when I am commiting. the commit command is send to
the server and fullfilled there but I still get a timeout. Any idea.
THX
-Dominik
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Dasarath,
before the tm.commit() on the client the transaction is active, the
commit is getting invoked on the server and completes fine, by catching
the timeoutException on the client I can see t hat the transaction has
the status 6. So it is pretty much ok except of the timeoutexception.
THX
-Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
