Problems staying connected to jabber.org
Paul Millar <[email protected]>
| Newsgroups | gmane.network.jabber.user |
|---|---|
| Message-ID | <[email protected]> |
Hi all, I've noticed a problem with staying connected to jabber.org, a problem that actually predates the recent outage. The problem is sporadic but clustered: it seems the client/server goes through a bad patch and then (some hours later) things seem to recover. I believe the cause is the jabber.org server sending the following message: <presence from="[email protected]/Kopete-work" type="unavailable" to="[email protected]/Kopete-work"/> I'm monitoring the connection to jabber.org using Kopete's XML Console. This uses a different colour for the two communication directions (client-to-server and server-to-client). The above message has the same colour as the opening fragment: <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' from='jabber.org' id='b9c991d1567330c3' version='1.0'> so I believe both messages to come from the jabber.org server. What appears to happen is the server sends an updated status to the client describing the client's own availability. I don't know XMPP enough to say if this is legal, but it looks fishy. Kopete honours the presence message and switches to an offline state (for the jabber.org connection) but the TCP connection remains established. Sometimes there are additional messages from jabber.org, despite the client being offline (for jabber.org). These seem mostly to be the status of (remote) accounts, so might be the results from status queries that were in- flight when the server told the client to go "offline". These messages received while "offline" can even trigger Kopete to "bounce". The sequence of states is online --> offline --> online. I guess this is achieved in the same fashion as going offline: a 'presence' message from the server; however this has happened only a few times and I wasn't capturing the XML stream during those times. The few times kopete "bounced" back online were always short lived. They were followed by kopete switching offline again: online --> offline --> online --> offline. I haven't seen kopete switch back online again having gone offline a second time. Manual intervention is needed .. but then kopete would switch back offline again after a short pause (a delay between a few seconds .. a few minutes) from another 'presence' message. Some time later (typically many hours, although it's hard to know exactly), the problem seems to recover. There no further indication of the problem and everything is fine. HTH, Paul. _______________________________________________ This is JUser -- a mailing list for end users of Jabber clients. To unsubscribe, send email to [email protected] or go to the following web page, scroll all the way down, and type in your email address: http://mail.jabber.org/mailman/listinfo/juser _______________________________________________