[jdev] Problem receiving presence after power outage

[dave at cridland.net]

I think you might see this if there's no XEP-0198 between servers and the old TCP session is still present on server2.

The presence response would go down this dead session, then it'd be detected as dead (TCP RST from server1), but typically the presence won't be resent, as it'll have been lost on the wire.

The solution is basically XEP-0198 on S2S links - you don't even need to do session resumption for it to be a substantial improvement here.

Sent from my android device.



-----Original Message-----
From: Kevin Smith <kevin at kismith.co.uk>
To: Jabber/XMPP software development list <jdev at jabber.org>
Sent: Wed, 21 Mar 2012 9:20 AM
Subject: Re: [jdev] Problem receiving presence after power outage

On Wed, Mar 21, 2012 at 9:12 AM, Mark Gabriel Paylaga
<mpaylaga at gmail.com> wrote:
> Hello,
>
> Has anyone tried this before? :
>
> 1.)  Server1 receives presence from Server2.
>
> 2.)  Power off Server1 (meaning no graceful exit, jabber still running and
> other services then literally just switch off the server or unplug it).
>
> 3.)  Restart Server1 (start all services including jabber).
>
> Result:  Server1 does not receive Server2's presence.
> Solution: Restart services in Server2.  Server1 will receive the presence.
>
> Is this because Server2 is still holding on to the old jabber session ID or
> something?

This shouldn't happen. When Server1 comes back online, it'll signal
that it wants presence for the newly online user at server1, and server2
should be willing to provide it (subject to subscription states being
right, etc.).

Is this a  general problem you see, or with specific services?

/K
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe at jabber.org
_______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20120321/2e20b1a3/attachment.html>