search

xmpp-ftw / xmpp-ftw-buddycloud

buddycloud extension for XMPP-FTW
Apache License 2.0
1 stars 1 forks source link

Slow return for media component discovery #22

Open martin-hewitt opened 10 years ago

martin-hewitt commented 10 years ago

When calling xmpp.buddycloud.discover.media-server, in the XMPP console, the following appears almost immediately, followed by an almost-60second gap, at which point I get the correct value returned to me on the socket:

2014-06-18T14:43:41.022Z - info: Stanza received: <iq id="218e7ddf-1726-40da-a5cf-32b6e85fd98a" type="result" to="me@example.com/resource" from="buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><query xmlns="http://jabber.org/protocol/disco#items"><item jid="mediaserver.buddycloud.org"/><item jid="directory.buddycloud.org"/><item jid="channels.buddycloud.org"/><item jid="topics.buddycloud.org"/><item jid="search.buddycloud.org"/><item jid="anon.buddycloud.org"/></query></iq>
2014-06-18T14:43:41.107Z - info: Stanza received: <iq id="030c2db2-66af-4f59-b682-1e2da3d07030" type="error" to="me@example.com/resource" from="directory.buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><error type="wait"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Component unavailable</text></error></iq>
2014-06-18T14:43:41.141Z - info: Stanza received: <iq id="f5bd0393-1782-4cfe-8b03-c7580db260c6" type="result" to="me@example.com/resource" from="mediaserver.buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><query xmlns="http://jabber.org/protocol/disco#info"><identity type="generic" name="Media Server" category="component"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="urn:xmpp:ping"/><feature var="jabber:iq:last"/><feature var="urn:xmpp:time"/><x xmlns="jabber:x:data" type="result"><field type="hidden" var="FORM_TYPE"><value>http://buddycloud.org/v1/api</value></field><field type="text-single" var="endpoint"><value>https://demo.buddycloud.org/api/media_proxy</value></field></x></query></iq>
2014-06-18T14:43:41.141Z - info: Stanza received: <iq id="898b70ef-0968-4fed-b8df-a79ecfa693e7" type="result" to="me@example.com/resource" from="channels.buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><query xmlns="http://jabber.org/protocol/disco#info"><identity type="channels" category="pubsub"/><identity type="inbox" category="pubsub"/><feature var="jabber:iq:register"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="jabber:iq:search"/></query></iq>
2014-06-18T14:43:41.195Z - info: Stanza received: <iq id="d6559b62-503e-431a-9b5a-07edf0d21ff4" type="error" to="me@example.com/resource" from="search.buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><error type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Server-to-server connection failed: Connecting failed: connection refused</text></error></iq>
2014-06-18T14:43:41.228Z - info: Stanza received: <iq id="3d8277cc-0800-4c79-a397-c6e1a3321f68" type="error" to="me@example.com/resource" from="anon.buddycloud.org" xmlns:stream="http://etherx.jabber.org/streams"><error type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Server-to-server connection failed: Connecting failed: connection refused</text></error></iq>
lloydwatkin commented 10 years ago

Interestingly if this is waiting for the timeout, then so is the discover mechanism (which has a lower default timeout of 8 seconds vs 30 seconds).

I'll take a look at this in the morning and make sure its working as expected (despite the tests saying it is).