Hi Hannes, well so far I can use the monitor to check on the soap messages for the web service invokations but not for checking on the messages send from the coordinator. Is there a way to monitor these messages too? I think the problem is the callback to the initiator, but so far I can't find what's going wrong... grrr.
thx -Dominik -------- Original-Nachricht -------- > Datum: Mon, 08 Oct 2007 11:41:48 +0200 > Von: Hannes Erven <[EMAIL PROTECTED]> > An: Dominik Heller <[EMAIL PROTECTED]> > CC: [email protected] > Betreff: Re: Help for Kandula 1 > Hi Dominik, > > > > org.apache.kandula.coordinator.TimedOutException > > at > org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:184) > > OK, this really is a timeout error. :-/ > > > As far as I know the code, those are the possible reasons: > > - The coordinator did not commit fast enough, e.g. because some resource > did not respond fast enough. > > - The coordinator did commit fast enough, but the callback to the > completion initiator failed. > > > In any case I guess it would be best to use the TCPMonitor again to > check what messages are actually transmitted between the parties and > whether they contain all required parameters and are addressed to the > correct parties. > > > -hannes -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
