Quoting Valerio Vianello <[EMAIL PROTECTED]>: Does your client run in a web container? I suspect your client is waiting for a response from the server (either COMMITTED or ABORTED) but is not getting that. Also, the response to COMMIT message comes on a different HTTP channel.
thanks, --dasarath > I'm a new kandula user. I have developed an example starting from the bankone > exemple that comes from the distribution. Client starts the transection > invokes two methods of the simpleservice and commit the transaction. The > problem that I have met is that the client after commit request remains > blocked as if it is waiting for a replay. Monitoring the comunication with > webScarab I have noticed that after the commit request from the client the > server answers with an http 200 OK. > > Can you suggest me what to do ???? > > Valerio > > P.S. this is the client stacktrace: > > [CallbackRegistry] registerCallback: timeout= 180000 > org.apache.kandula.coordinator.TimedOutException > at > org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI > mpl.java:184) > at > org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(Trans > actionManagerImpl.java:63) > at > kandulaMio.ServizioTransazionale.main(ServizioTransazionale.java:93) > java.lang.RuntimeException: org.apache.kandula.coordinator.TimedOutException > at > org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI > mpl.java:191) > at > org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(Trans > actionManagerImpl.java:63) > at > kandulaMio.ServizioTransazionale.main(ServizioTransazionale.java:93) > Caused by: org.apache.kandula.coordinator.TimedOutException > at > org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI > mpl.java:184) > ... 2 more > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
