Hi there, I just found (last night) a rather embarrassing bug in the federation code. The XmppFederationHostForDomain code caches disco results from the first time it sees a reference to a domain. If the domain happens to be down, wavesandbox won't talk to that domain again until the federation gateway is restarted. I have a fix in hand locally, just doing a whole pile of testing and will try to push it out to wavesandbox.com next week (as well as pushing it to the waveprotocol hg repository as soon as possible, as it also affects fedone)
In the mean time, I'll keep an eye on the logs and kick the relevant federation gateway server when I see it's picked up a dud result. I'm just restarting it now. Terribly sorry, Anthony On Thu, Mar 25, 2010 at 14:17, James Purser <[email protected]> wrote: > On Wed, 2010-03-24 at 19:51 -0700, antwatkins wrote: >> Has anyone else had trouble federating with wavesandbox today? I >> could federate yesterday without issue. Just to be sure I cloned the >> current version of FedOne and ran that. I extended the timeout. In >> each case, I received an UNDEFINED_CONDITION error code (when it >> didn't timeout first). Anyone else seen this? >> >> Thanks, >> >> Anthony > > Yeah I'm getting the following with wave-mongodb: > > WARNING: Received response packet without paired request: > nPh5l8/xhvYAAAAAAAAAAw== > 25/03/2010 2:15:01 PM org.waveprotocol.wave.federation.xmpp.RemoteDisco > $1$1 error > INFO: Remote server wavesandbox.com failed on disco items: > UNDEFINED_CONDITION > 25/03/2010 2:15:01 PM org.waveprotocol.wave.federation.xmpp.XmppManager > response > WARNING: Received response packet without paired request: > eEWSqQAQy7EAAAAAAAAAAg== > 25/03/2010 2:15:01 PM org.waveprotocol.wave.federation.xmpp.RemoteDisco > requestDiscoInfo > INFO: Sending disco info request for: wavesandbox.com > 25/03/2010 2:15:01 PM org.waveprotocol.wave.federation.xmpp.RemoteDisco > requestDiscoInfo > INFO: Sending disco info request for: wave.wavesandbox.com > 25/03/2010 2:15:21 PM org.waveprotocol.wave.federation.xmpp.RemoteDisco > finish > INFO: Could not discover remote JID: error_code: REMOTE_SERVER_TIMEOUT > for wavesandbox.com > 25/03/2010 2:15:21 PM > org.waveprotocol.wave.federation.xmpp.XmppFederationHostForDomain > discoFailed > WARNING: Disco failed for wavesandbox.com, failing 2 queued messages > 25/03/2010 2:15:21 PM > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl$4 > onFailure > WARNING: outgoing waveletDeltaUpdate failure: error_code: > RESOURCE_CONSTRAINT > error_message: "error_code: REMOTE_SERVER_TIMEOUT\n" > > 25/03/2010 2:15:21 PM > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl$5 > onFailure > WARNING: outgoing waveletCommitUpdate failure: error_code: > RESOURCE_CONSTRAINT > error_message: "error_code: REMOTE_SERVER_TIMEOUT\n" > > 25/03/2010 2:16:01 PM org.waveprotocol.wave.federation.xmpp.XmppManager > response > WARNING: Received response packet without paired request: > VajktFBBzyIAAAAAAAAABQ== > > -- > James Purser > http://wavingtheshiny.collaborynth.com.au > Wave Addresses: > [email protected] (wave.google.com) > [email protected] (wavesandbox.com) > [email protected] (collaborynth.com.au FedOne Server) > Skype: purserj1977 > GTalk: [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. > > -- 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.
