Jro
Show profile
Link to this post
Subject: 1.2.0 -> 1.2.1 Issue
I decided to play with the 1.2.1 DLL on the mobile in some quick prototype apps that worked fine with logging in using the 1.2.0 DLL. Transitioning to the latest 1.2.1 version caused my application to hang. I isolated it to the _xmppClient.Login never returning from completion, essentially hanging with no subsequent OnLogin, OnClose, or OnError events firing.
As a quick I test, I pulled up the sample client and attempted to use it with the included 1.2.1 DLL and had no joy connecting. The following is the debug XML:
At this point, the login simply hangs as described above. I do not think a time out error would even fired after two minutes.
I then reverted the sample client to a 1.2.0 version of the Matrix DLL and everything behaved as normal. I did the sample client tests with Openfire, although I tested my original prototype app with both OpenFire and ejabberd. I've placed the successful 1.2.0 output of the debug xml tab in the following pastebin link:
http://pastebin.com/Qxg75pcZ
Jeffrey
As a quick I test, I pulled up the sample client and attempted to use it with the included 1.2.1 DLL and had no joy connecting. The following is the debug XML:
SEND: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" to="folka" version="1.0" >
RECV: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="folka" id="454e5f5" xml:lang="en" version="1.0" >
RECV: <stream:features xmlns:stream="http://etherx.jabber.org/streams">
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>DIGEST-MD5</mechanism>
<mechanism>PLAIN</mechanism>
<mechanism>ANONYMOUS</mechanism>
<mechanism>CRAM-MD5</mechanism>
</mechanisms>
<compression xmlns="http://jabber.org/features/compress">
<method>zlib</method>
</compression>
<auth xmlns="http://jabber.org/features/iq-auth" />
<register xmlns="http://jabber.org/features/iq-register" />
</stream:features>
RECV: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="folka" id="454e5f5" xml:lang="en" version="1.0" >
RECV: <stream:features xmlns:stream="http://etherx.jabber.org/streams">
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>DIGEST-MD5</mechanism>
<mechanism>PLAIN</mechanism>
<mechanism>ANONYMOUS</mechanism>
<mechanism>CRAM-MD5</mechanism>
</mechanisms>
<compression xmlns="http://jabber.org/features/compress">
<method>zlib</method>
</compression>
<auth xmlns="http://jabber.org/features/iq-auth" />
<register xmlns="http://jabber.org/features/iq-register" />
</stream:features>
At this point, the login simply hangs as described above. I do not think a time out error would even fired after two minutes.
I then reverted the sample client to a 1.2.0 version of the Matrix DLL and everything behaved as normal. I did the sample client tests with Openfire, although I tested my original prototype app with both OpenFire and ejabberd. I've placed the successful 1.2.0 output of the debug xml tab in the following pastebin link:
http://pastebin.com/Qxg75pcZ
Jeffrey
This post was edited 2 times, last on 2010-04-07, 17:58 by