OK,
the client does not stop automatically. 180secs after the commit was
called, there is a timeout fault on the server.
Can you please check if client-config.wsdd was deployed correctly also
on the server, and whether all messages contain WS-Addressing (To, From,
...)-elements?
Moreover I thought that
the coordinator would call either prepare or commit of my service. This
is not the case.
The coordinator does call Prepare and later either Rollback or Commit on
your _participant_. The participant is a kandula component (its more or
less the transaction manager) that does many protocol specific things
for you.
One of them is that it automatically responds to the prepare message
after polling all locally enlisted transaction ressources, and if they
are prepared, your whole participant is.
When receiving a commit/rollback notification from the coordinator,
their decicision is likewise forwarded to all local resources.
This was done for your convenience: just enlist all resources you used
in the global transaction, and they will automagically be committed or
rolled back -- your service shouldn't be doing something fundamentally
different, btw ;-)
If you want explicit control over prepare/commit, you'll have to enlist
a custom ressource in the ongoing transaction (with the transaction
manager). If you do so, the TransactionManager will automatically ask it
for preparedness and later tell the transaction result.
Some test cases in the Testsuite use this pattern to emulate resouce
errors, so you may look there to see some examples.
best regards,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
