Dasarath Weeratunge schrieb:
Quoting Dominik <[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.
It should not be possible for you to catch the server side exception I mentioned
earlier on the client side. Perhaps we are talking about different things here.
-- Dasarath
THX
-Dominik
---------------------------------------------------------------------
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]
What I meant earlier, is that on the client side I have wrapped the
tm.begin() and the tm.commit() with a try/catch block. In addition I
have some system.outs on the server side in the commit method. as soon
as the client invokes the tm.commit() the server side works fine and
comes to an end but on the client side I get a timeoutException which I
catch because of the try/catch block. After catching the exception I
invoke the getBalances Method and there it says no transaction on the
server side.
thx
-Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
