The XMPP server that wavesandbox.com talks to doesn't understand disco at all. This is a known problem, but fixing it is a non-trivial exercise. In the meantime, we fall back to trying "wave.foo" if this happens. I don't know enough about ejabberd to confirm what it might be doing....
On Thu, Nov 5, 2009 at 13:23, Brian May <[email protected]> wrote: > > On Wed, Nov 04, 2009 at 05:22:37PM -0800, Tad Glines wrote: >> >> In the FedOne log output you'll see a sequence similar to the following: >> >> <iq type="get" id="9437-3" to="wavesandbox.com" from="wave.glines.com"> >> <query xmlns="http://jabber.org/protocol/disco#items"/> >> </iq> >> >> <iq type="error" id="9437-3" to="wave.glines.com" from="wavesandbox.com"> >> <query xmlns="http://jabber.org/protocol/disco#items"/> >> <error code="404" type="cancel"> >> <remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> >> </error> >> </iq> >> >> <iq type="get" id="9320-4" to="wave.wavesandbox.com" from="wave.glines.com"> >> <query xmlns="http://jabber.org/protocol/disco#info"/> >> </iq> >> >> <iq type="result" id="9320-4" from="wave.wavesandbox.com" >> to="wave.glines.com"> >> <query xmlns="http://jabber.org/protocol/disco#info";> >> <identity category="collaboration" type="google-wave" name="Google >> Wave Server"/> >> <feature var="http://waveprotocol.org/protocol/0.2/waveserver"/> >> </query> >> </iq> >> >> It's normal to get the "remote-server-not-found" for wavesandbox.com. >> But you should get a valid response to the query of >> wave.wavesandbox.com. > > Ok, so it looks like the jabber server returns a failure response to Fedone, > which then tries again with the hardcoded "wave." + domain. > > My ejabber server is constantly trying to connect to wavesandbox.com > xmpp-server port, and never returns the error back to Fedone, so Fedone never > gets a chance to try again. Or thats how it looks anyway. > > Which raises the question, when working, why does the Jabber server return > 404? Is this in response to a TCP timeout error? Or is there something > else that is different here? > > As it is I am finding it hard to find fault in what my Jabber server is doing, > except maybe it shouldn't keep retrying endlessly. > -- > Brian May <[email protected]> > > > > -- Anthony Baxter, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
