[jitsi-dev] Invalid DiscoverInfo for http://swift.im#...


#1

I see the appended lines in the log and have two questions:

1. Why does swift.im apear in the logs? I do not have an account at
swift.im. I do have an account at jabber.org. jingle1.jabber.org is
currently unavailable according to PSI+.

2. Do those "Invalid DiscoverInfo" errors indicate an error originating
at swift.im or is something within Jitsi incorrect?

Cheers,
Andreas

···

---

20:12:05.897 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2003 Start
Jingle Nodes
discovery!

20:12:06.860 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@5edd2434

20:12:07.318 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@63fbae11

20:12:07.570 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@89864bbb
20:12:22.695 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2013 Jingle
Nodes discovery
terminated!

20:12:22.696 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2014 Found
0 Jingle Nodes relay


#2

I modified the discoverInfo method to output the entityID and now see this:

21:38:36.847 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@11a1c6e2 entityID:
stpeter@jabber.org/117ec05d4c06d3fc
21:38:37.995 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@ad796834 entityID:
stpeter@jabber.org/117ec05d4c06d3fc
21:38:39.641 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@b44ccab0 entityID:
stpeter@jabber.org/117ec05d4c06d3fc

Cheers,
Andreas

···

--

Am 13.06.2011 21:17, schrieb Andreas Kuckartz:

I see the appended lines in the log and have two questions:

1. Why does swift.im apear in the logs? I do not have an account at
swift.im. I do have an account at jabber.org. jingle1.jabber.org is
currently unavailable according to PSI+.

2. Do those "Invalid DiscoverInfo" errors indicate an error originating
at swift.im or is something within Jitsi incorrect?

Cheers,
Andreas
---

20:12:05.897 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2003 Start
Jingle Nodes
discovery!

20:12:06.860 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@5edd2434

20:12:07.318 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@63fbae11

20:12:07.570 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@89864bbb
20:12:22.695 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2013 Jingle
Nodes discovery
terminated!

20:12:22.696 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2014 Found
0 Jingle Nodes relay


#3

1. Why does swift.im apear in the logs? I do not have an account at
swift.im. I do have an account at jabber.org. jingle1.jabber.org is
currently unavailable according to PSI+.

swift.im appearing in your logs in relation to DiscoverInfo given that
you don't use the client in question yourself means that a contact in
your contact list is using Swift as their XMPP client.

2. Do those "Invalid DiscoverInfo" errors indicate an error originating
at swift.im or is something within Jitsi incorrect?

We'll have to check it out but, as you've probably seen in the code
already, the receipt of invalid DiscoverInfo is expected so it does
not necessarily indicate a case of an error on Jitsi's side.

···

On Mon, Jun 13, 2011 at 10:17 PM, Andreas Kuckartz <A.Kuckartz@ping.de> wrote:


#4

I further researched that and Kev helped me in the
xmpp:swift@rooms.swift.im chatroom.

As far as I understand it at the moment the error might be that there is
no error (false alarm raised by warning).

In
impl.protocol.jabber.extensions.caps.EntityCapsManager.isValid(DiscoverInfo
discoverInfo) in these lines

           boolean valid =
                (discoverInfo != null)
                    && getNodeVer().equals(discoverInfo.getNode())
                    && ...

the expression discoverInfo.getNode() for some reason is null before the
warning logged.

So my question is: should discoverInfo.getNode() be different from null
here ?

Cheers,
Andreas

···

Am 13.06.2011 21:47, schrieb Andreas Kuckartz:

I modified the discoverInfo method to output the entityID and now see this:

21:38:36.847 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@11a1c6e2 entityID:
stpeter@jabber.org/117ec05d4c06d3fc
21:38:37.995 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@ad796834 entityID:
stpeter@jabber.org/117ec05d4c06d3fc
21:38:39.641 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@b44ccab0 entityID:
stpeter@jabber.org/117ec05d4c06d3fc

Cheers,
Andreas
--

Am 13.06.2011 21:17, schrieb Andreas Kuckartz:

I see the appended lines in the log and have two questions:

1. Why does swift.im apear in the logs? I do not have an account at
swift.im. I do have an account at jabber.org. jingle1.jabber.org is
currently unavailable according to PSI+.

2. Do those "Invalid DiscoverInfo" errors indicate an error originating
at swift.im or is something within Jitsi incorrect?

Cheers,
Andreas
---

20:12:05.897 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2003 Start
Jingle Nodes
discovery!

20:12:06.860 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@5edd2434

20:12:07.318 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@63fbae11

20:12:07.570 SCHWERWIEGEND:
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().477
Invalid DiscoverInfo for http://swift.im#XH3meI11JZj00/DhOlop7p7jKBE=:
org.jivesoftware.smackx.packet.DiscoverInfo@89864bbb
20:12:22.695 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2013 Jingle
Nodes discovery
terminated!

20:12:22.696 INFO:
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.run().2014 Found
0 Jingle Nodes relay