Quoting Jack Wang <[EMAIL PROTECTED]>: > In my ws impl, if there is no ut explicitly used, I can use tx.rollback() in > impl to tell the > kandula to rollback the global tx. In this case, when wstm.commit() is > excuted, it will reports
I don't understand what you are talking here. Please tell me the state of the activity at both ends or tell me the messages sent and received in order. Without knowing the state of each entity you cannot debug applications of this nature. > exception: "The message was invalid for the current state of the activity.". are you trying to commit/rollback the tx at the server end? > In the test, after the client began, 2 or 3 seconds later, the ws s finished, > but more then 9 > seconds later, the "wstm.commit()" command was carried out. It seems > "wstm.commit()" spends too Kandula in its default configuration will terminate transactions after 180 *seconds*. Change this timeout to whatever value suitable for you and rebuild. The constant is defined in the class o.a.k.coordinator.CallbackRegistry. However, this value has been sufficient in all the testing that I've done thus far. --dasarath > > > > > > > ___________________________________________________________ > ÑÅ»¢1GÃâ·ÑÓÊÏä°Ù·Ö°Ù·ÀÀ¬»øÐÅ > http://cn.mail.yahoo.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
