Client provided invalid session?

Openfire Openfire Support
1

EDIT: sorry, it seems I mixed up two different problems, hence the change in title and logs be patient

So I am playing around with Openfire 3.7.0 Beta and the Strophe library (BOSH).

If I leave the client to do nothing for a while (less than 2 mins), the server just kills the session, in the Warnings:

2011.03.01 22:53:43 Deliverable unavailable for 3631268666 2011.03.01 22:53:44 Client provided invalid session: ea84fe08. [10.211.55.2]

Is someone familiar with this? This doesn’t happen using spark.

What I see logging from Strophe:

<stream:features>
<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>
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'/>
<session xmlns='urn:ietf:params:xml:ns:xmpp-session'/>
</stream:features>
<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
      mechanism='DIGEST-MD5'/>
<challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
cmVhbG09InBvbmdlbGxzLmxvY2FsIixub25jZT0iQU9vOUJrc2RBVmQ0ZTNSbGZBcG5TRnptcldjM0xHaFI5MW05allGViIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==
</challenge>
<response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
dXNlcm5hbWU9InRlc3QiLHJlYWxtPSJwb25nZWxscy5sb2NhbCIsbm9uY2U9IkFPbzlCa3NkQVZkNGUzUmxmQXBuU0Z6bXJXYzNMR2hSOTFtOWpZRlYiLGNub25jZT0iZDQxZDhjZDk4ZjAwYjIwNGU5ODAwOTk4ZWNmODQyN2UiLG5jPSIwMDAwMDAwMSIscW9wPSJhdXRoIixkaWdlc3QtdXJpPSJ4bXBwL3BvbmdlbGxzLmxvY2FsIixyZXNwb25zZT0iYjMwYThhZGI2ODE1NTM4YjRmMTA2NGRiNjZmMWQ4YjciLGNoYXJzZXQ9InV0Zi04Ig==
</response>
<success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
cnNwYXV0aD01NDVhZDc0YWEyZTNlNTUzMDA0ZTNiZDdmNGMwYzUyNQ==
</success>
<stream:features>
<compression xmlns='http://jabber.org/features/compress'>
<method>
zlib
</method>
</compression>
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'/>
<session xmlns='urn:ietf:params:xml:ns:xmpp-session'/>
</stream:features>
<iq type='set'
    id='_bind_auth_2'
    xmlns='jabber:client'>
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
<resource>
console
</resource>
</bind>
</iq>
<iq xmlns='jabber:client'
    type='result'
    id='_bind_auth_2'
    to='pongells.local/ea84fe08'>
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
<jid>
test@pongells.local/console
</jid>
</bind>
</iq>
<iq type='set'
    id='_session_auth_2'
    xmlns='jabber:client'>
<session xmlns='urn:ietf:params:xml:ns:xmpp-session'/>
</iq>
<iq xmlns='jabber:client'
    type='result'
    id='_session_auth_2'
    to='test@pongells.local/console'>
<session xmlns='urn:ietf:params:xml:ns:xmpp-session'/>
</iq>
<presence xmlns='jabber:client'>
<priority>
10
</priority>
</presence>
<presence xmlns='jabber:client'>
<priority>
10
</priority>
</presence>
<presence xmlns='jabber:client'
          type='unavailable'/>

At this point I am disconnected… duh.

2

Hello,

Are you still having troubles? Is your strophe client making a new request at least every 30 seconds? if not, the server may terminate the session. I changed the server property:

xmpp.httpbind.client.idle to 300

and had better success.

daryl

3

I found i fixed this when my server name (in server properties) didn’t match the host name the client was connecting with.

4

Thank you both, in the end I decided not to use Strophe and stick with the usual TCP connection method. Therefore, I could not try your suggestions.