Gerald, Thanks! Does the wave not appear if you search for it in the wavesandbox interface? Can you also try adding [email protected] the next time you try it?
Thanks, -joe On Fri, Feb 26, 2010 at 11:28 AM, Gerald <[email protected]> wrote: > I am using my personal domain "zhenhua.info" and subdomain is > "wave1.zhenhua.info". > I tested it on Feb 24 and Feb 26. > > Log when federated with **initech-corp.com**. > > ----------------------- Starting server --------------------------- > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl <init> > INFO: Wave Server configured to host local domains: > [wave1.zhenhua.info] > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.ServerMain > $RpcInetSocketAddressFactory <init> > INFO: Starting client frontend on host: wave1.zhenhua.info port: 9876 > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > initialize > INFO: initializing with JID: wave.wave1.zhenhua.info > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > start > INFO: connected to XMPP server with JID: wave.wave1.zhenhua.info > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppDisco > sendDiscoItemsGet > INFO: Trying to discover remote server: initech-corp.com > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processPacket > INFO: received XMPP packet: > > <iq type="get" id="505-11" from="component.wave1.zhenhua.info" > to="wave.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#info"/> > </iq> > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processIqPacket > INFO: key for this error is > org.xmpp.packet.IQ:component.wave1.zhenhua.info:505-11 > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <iq type="result" id="505-11" from="wave.wave1.zhenhua.info" > to="component.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#info";> > <identity category="collaboration" type="google-wave" name="Google > Prototype Wave Server - FedOne"/> > <feature var="http://waveprotocol.org/protocol/0.2/waveserver"/> > </query> > </iq> > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <iq type="get" id="651-0" to="initech-corp.com" > from="wave.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#items"/> > </iq> > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: key for this error is org.xmpp.packet.IQ:initech-corp.com:651-0 > Feb 26, 2010 10:56:39 AM > org.waveprotocol.wave.examples.fedone.ServerMain run > INFO: Starting server > Feb 26, 2010 10:56:43 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processPacket > INFO: received XMPP packet: > > <iq type="result" id="651-0" from="initech-corp.com" > to="wave.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#items";> > <item jid="wave.initech-corp.com" name="FedOne"/> > </query> > </iq> > Feb 26, 2010 10:56:43 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processIqPacket > INFO: key for this error is org.xmpp.packet.IQ:initech-corp.com:651-0 > Feb 26, 2010 10:56:43 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <iq type="get" id="5293-1" to="wave.initech-corp.com" > from="wave.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#info"/> > </iq> > Feb 26, 2010 10:56:43 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: key for this error is org.xmpp.packet.IQ:wave.initech-corp.com: > 5293-1 > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processPacket > INFO: received XMPP packet: > > <iq type="result" id="5293-1" from="wave.initech-corp.com" > to="wave.wave1.zhenhua.info"> > <query xmlns="http://jabber.org/protocol/disco#info";> > <identity category="collaboration" type="google-wave" > name="FedOne"/> > <feature var="http://waveprotocol.org/protocol/0.2/waveserver"/> > </query> > </iq> > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processIqPacket > INFO: key for this error is org.xmpp.packet.IQ:wave.initech-corp.com: > 5293-1 > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppDisco > $DiscoItemIterator run > INFO: Discovered remote JID: wave.initech-corp.com for initech- > corp.com > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > transmitDummyMessage > INFO: sending ping message: > > <message type="normal" to="wave.initech-corp.com" > from="wave.wave1.zhenhua.info" id="9197-2"> > <ping xmlns="http://waveprotocol.org/protocol/0.2/waveserver"/> > <request xmlns="urn:xmpp:receipts"/> > </message> > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <message type="normal" to="wave.initech-corp.com" > from="wave.wave1.zhenhua.info" id="9197-2"> > <ping xmlns="http://waveprotocol.org/protocol/0.2/waveserver"/> > <request xmlns="urn:xmpp:receipts"/> > </message> > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processPacket > INFO: received XMPP packet: > > <message id="9197-2" to="wave.wave1.zhenhua.info" from="wave.initech- > corp.com"> > <received xmlns="urn:xmpp:receipts"/> > </message> > Feb 26, 2010 10:56:45 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processMessageReceipt > INFO: got ping response from initech-corp.com > > <message id="9197-2" to="wave.wave1.zhenhua.info" from="wave.initech- > corp.com"> > <received xmlns="urn:xmpp:receipts"/> > </message> > ----------------------------- end starting server > ------------------------- > > From the log, I can tell ping succeeds. > > Then I use "./run-client-console.sh username" to test it. I created a > new wave and added my wavesandbox account to it. Then I typed some > messages, the log became really long. I picked the part which I think > may be important: > > ---------------------------- for blips > ------------------------------------ > Feb 26, 2010 11:12:00 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <iq type="result" id="/c6ecuvzyLkAAAAAAAABfQ==" > from="wave.wave1.zhenhua.info" to="wave.wavesandbox.com"> > <pubsub xmlns="http://jabber.org/protocol/pubsub";> > <items> > <item> > <applied-delta xmlns="http://waveprotocol.org/protocol/0.2/ > waveserver"><! > [CDATA[CscDCpoBCjYIABIyd2F2ZTovL3dhdmUxLnpoZW5odWEuaW5mby93K2U1QzVocnJQdzVSOS9jb252K3Jvb3QSGWdlcmFsZEB3YXZlMS56aGVuaHVhLmluZm8aGwoZZ2VyYWxkQHdhdmUxLnpoZW5odWEuaW5mbxooGiYKDGNvbnZlcnNhdGlvbhIWChAaDgoMY29udmVyc2F0aW9uCgIgARKnAgqAAkmhLHeGyMTwsO84yaQlT/ > bjEJdK/Ec45r9bguleBWrlbnIGCVmwc4ZKVxo1Fe6SFE+6pGG+dg/ > GDXlEGu57ykiRUiSbAMf6UfC9Vdoc7lDxWyCC8ySUYv9EU/ > eYg6UEdQenj2KUuinyxcH5YYIVuNCEK7Vtrw2lR6DOhZrViXv1E5AYCu1gv58IxGBwrUpzwYA4QS9Rcn > +HrFtYygOT7ECDXOPfvAMGq5MMlC+A > +Ju3gxrDaJFToF2rm6JT6hWjpsQ6iDc3QYjKdfQZ1R4GWTVHg0GtNbCcLrLFHnh3dANdNhp9p > ++8rQpoi+ZpAuEse+DjO4G05NzdBUPdaZmphuYSIABoyVP+2HN/ > XvVXqhyLHx4FtOfMHe5h0Qpp9x3pFpa7GAESNggAEjJ3YXZlOi8vd2F2ZTEuemhlbmh1YS5pbmZvL3crZTVDNWhyclB3NVI5L2NvbnYrcm9vdBgCINqZptjwJA==]]></ > applied-delta> > </item> > <item> > <applied-delta xmlns="http://waveprotocol.org/protocol/0.2/ > waveserver"><! > [CDATA[CvsCCk8KGAgCEhRBSeQkheafsDxezXwqEJGs2XfxYBIZZ2VyYWxkQHdhdmUxLnpoZW5odWEuaW5mbxoYChZqZW52b3JAd2F2ZXNhbmRib3guY29tEqcCCoAC5k3gt4S1ryZAt/ > tNloQ5TnGr9f4p9d3yHdY10wv2j > +MkC8AAXfiBFwyYqPH9ZWfs218p4KO1ZIq97UH2lTmkwaXMWPhSvxlyuyrP > +cnyEArHC6inTfEXWlWFgAWDs9bl6EqsFnaOlczTZnY71o+0+W7v/2nWz > +ug0rVgSgXAVZtyNcZwjt+6VQfPowjtHSagJgzvkPa86uhdXKOaM > +EPkd0K40E8zO4Ao9HWLiykoz74aad3RkF48PfRofDNZkGlIkKQAmC74R67wycIpbaFB8RL2O > +4K9J3mQ9tpsFwsNc9Fvf5cN4/G0CEqyUfLpxnnqcervcr7w5It+mCEWNNQxIgAGjJU/ > 7Yc39e9VeqHIsfHgW058wd7mHRCmn3HekWlrsYARIYCAISFEFJ5CSF5p > +wPF7NfCoQkazZd/FgGAEgssGq2PAk]]></applied-delta> > </item> > <item> > <commit-notice xmlns="http://waveprotocol.org/protocol/0.2/ > waveserver" version="3"/> > </item> > <item> > <history-truncated xmlns="http://waveprotocol.org/protocol/0.2/ > waveserver" version="3"/> > </item> > </items> > </pubsub> > </iq> > Feb 26, 2010 11:12:00 AM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > processPacket > INFO: received XMPP packet: > > <iq type="get" id="rXVSkzdQICYAAAAAAAABfg==" > from="wave.wavesandbox.com" to="wave.wave1.zhenhua.info"> > <pubsub xmlns="http://jabber.org/protocol/pubsub";> > <items node="wavelet"> > <delta-history xmlns="http://waveprotocol.org/protocol/0.2/ > waveserver" start-version="0" start-version- > hash="d2F2ZTovL3dhdmUxLnpoZW5odWEuaW5mby93K2U1QzVocnJQdzVSOS9jb252K3Jvb3Q=" > end-version="3" end-version-hash="ReelYXF5LfbqhRSKOKtbVTI6N1w=" > wavelet-name="wave://wave1.zhenhua.info/w+e5C5hrrPw5R9/conv+root"/> > </items> > </pubsub> > </iq> > -------------------------------------------------------------------------- > > It seems that my server and wavesandbox can communicate with each > other. > > But the messages just did not pop up in wavesandbox user interface. > > I also tried *acmewave.com*, the log is similar to what is shown > above. > > I tried *wavesandbox.com* as well, no luck. > > When I used top-level domain, federation with "initech-corp.com" was > successful. > > > Thanks, > Gerald > > > On Feb 26, 1:42 am, Joe Gregorio <[email protected]> wrote: >> Gerald, >> Yes, sub-domains should work. What is the domain name >> you are using and when is the time and date when you last >> ran your test against wavesandbox? >> >> Thanks, >> -joe >> >> -- >> Joe Gregorio >> Developer Relations, Google Wave >> >> On Wed, Feb 24, 2010 at 8:00 PM, Gerald <[email protected]> wrote: >> > I tried using both top-level domain and subdomain for federation. >> > I obtained corresponding CA-issued certificates for them and changed >> > run-config.sh accordingly. Also XMPP server OpenFire configuration was >> > changed accordingly. >> >> > Top-level domain works while subdomain does not work. >> >> > For subdomain, it seems connection between my XMPP server and wave >> > server are connected (ping succeeds) and blips are sent and >> > acknowledged. But the message does not pop up in wave sandbox user >> > interface. >> > I wonder whether wave sandbox server treats subdomains differently >> > from top-level domains. Even if all configurations are correct, using >> > subdomain still won't work? >> >> > This pagehttp://code.google.com/p/wave-protocol/wiki/Federation >> > introduces the procedure of connection establishment. In the example >> > top-level domain (other.com) is used. I assume if I replace other.com >> > with sub.other.com, it will work. >> >> > Thanks >> > Gerald >> >> > -- >> > 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 >> > athttp://groups.google.com/group/wave-protocol?hl=en. >> >> > > -- > 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. > > -- 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.
