Bug in Stream Managament?

Hi,

I am having a problem with Stream Management in the beta1 version. It looks like the handleCount is not initialised at the right time and therefor I keep getting a “h attribute too big” error from the server. It looks like the packets that are sent in between mess up the counting. As a result, the connection is taken down, re-established, taken down, etc. Smack becomes unusable.

A possible solution might be for Smack to send first and then . So basically enable Stream Management before opening a session (since the session is opened all messages are possible to route to the client’s TCP socket).

Thanks,
Andrej

SEND (0): <stream:stream xmlns=‘jabber:client’ to=‘localhost’ xmlns:stream=‘http://etherx.jabber.org/streams’ version=‘1.0’>

RECV (0): <?xml version='1.0'?><stream:stream xmlns=‘jabber:client’ xmlns:stream=‘http://etherx.jabber.org/streams’ id=‘1738634034’ from=‘localhost’ version=‘1.0’ xml:lang=‘en’>

RECV (0): stream:featuresDIGEST-MD5SCRAM-SHA-1PLAIN<register xmlns='http://jabber.org/features/iq-register’/></stream:features>

XMPPConnection connected (0)

SENT (0): biwsbj0zOGQwYzBlOGNmZDI0NTIyODM1ZGI3MDAyZTY1YTk1OSxyPWB TXTUmO0dOYFhTSj5uS01EYn5cMFx3cXFfXWNuZE12

RECV (0): cj1gU101JjtHTmBYU0o+bktNRGJ+XDBcd3FxX1 1jbmRNdmFINm9UdzNQTU5UQVgxUTRRcDdYamc9PSxzPUN2RWpiWkQ1dUIwOVpPMVExbVVXZVE9PSxpPT QwOTY=

SENT (0): Yz1iaXdzLHI9YFNdNSY7R05gWFNKPm5LTURifl wwXHdxcV9dY25kTXZhSDZvVHczUE1OVEFYMVE0UXA3WGpnPT0scD04aUp1bXd1Ris4NWRhejRKSURqTz Q4dm9FR2c9

RECV (0): dj10MmhJRmoxQk14bHB5RDhDVFU4aFVRaWJjdT Q9

SENT (0): <stream:stream xmlns=‘jabber:client’ to=‘localhost’ xmlns:stream=‘http://etherx.jabber.org/streams’ version=‘1.0’>

SENT (0):

RECV (0): <?xml version='1.0'?><stream:stream xmlns=‘jabber:client’ xmlns:stream=‘http://etherx.jabber.org/streams’ id=‘164996246’ from=‘localhost’ version=‘1.0’ xml:lang=‘en’>stream:features<register xmlns='http://jabber.org/features/iq-register’/></stream:features>

RECV (0):

SENT (0): android/38a332ee3de6e61a</re source>

RECV (0): 38d0c0e8cfd24522835db7002e65a959@ localhost/android/38a332ee3de6e61a

SENT (0):

RECV (0):

SENT (0):

RECV (0):

SENT (0):

User logged (0): 38d0c0e8cfd24522835db7002e65a959@localhost:5222/android/38a332ee3de6e61a

SENT (0):

SENT (0):

XMPPConnection authenticated (0)

XMPPConnection reconnected (0)

SENT (0):

SENT (0):

RECV (0):

RECV (0):

SENT (0):

RECV (0):

RECV (0):

SENT (0):

SENT (0):

RECV (0):

SENT (0):

RECV (0):

SENT (0):

RECV (0): stream:errorh attribute too big</stream:error></stream:stream>

01-29 08:25:31.527 1362-1422/com.fansz W/AbstractXMPPConnection﹕ Connection closed with error

stream:errorh attribute too big</stream:error>

at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPC onnection.java:968)

at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$200(XMPPTCPCon nection.java:902)

at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnecti on.java:921)

01-29 08:25:31.527 1362-1422/com.fansz I/ImManager﹕ connectionClosedOnError(Exception e)

Which version of Smack did you use? Did you try the latest beta2-SNAPSHOT?

Nope I used the beta1 version.

Please try the beta2-SNAPSHOT.

Hi,

FYI, I have not seen this problem since I am using beta2-SNAPSHOT.

Cheers,

Andrej