Hi Ruban, > > the third question...if I comment the line > > wstm.commit() of the client code...why dont I see the > > message soap (in tcpmonitor) asociated to the > > registrationService? (I only see the > > activationCoordiantor)It is supposed that the > > wstm.commit() doesn't generate the registration of the > > ctx but the called to serviceX.method(), doesn't it? > > This is connected to the previous question. wstm.commit() registers for > the CompletionProtocol, and I guess this is the call to the registration > service you see in the tcpmonitor (and that disappears if you comment > out that line). > > You are right that normally, before the initiator issues the > commit/rollback command, ressources are registered. I suspect that your > test service does not correctly do this, and you hence don't see more > registration requests. >
also, when you comment out wstm.commit your client will not register for completion protocol; it will also not commit the transaction. A participant registers for completion only if it needs to terminate a transaction. So registration for Completion happens at the very end. The reason is TransactionImpl is also used by participants who use one of the 2PC protocols to interact with the coordinator- such as your serviceX. If the registration happened up front (when the TransactionImpl object is created), it could be unnecessary. thanks, --dasarath --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
