Hello, I've searched in the internet and it seems that jabberd1.4 does not support the XEP-0198. Am I correct? If this is so, do i need to modify my jabberd1.4 files to support this? or is it better just to send a message to the services in server2 to restart once server1 has restarted?
On Wed, Mar 21, 2012 at 10:57 PM, Mark Gabriel Paylaga <mpayl...@gmail.com>wrote: > Thanks for the quick response. > It's with a particular windows client that uses jabber of server1 to > communicate with a service in server2 which also uses jabber. > I'll checkout the XEP-0198... By the way We're using jabber 1.4 in the > servers and centos4. > > On Wed, Mar 21, 2012 at 5:50 PM, <d...@cridland.net> wrote: > >> 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 <ke...@kismith.co.uk> >> To: Jabber/XMPP software development list <jdev@jabber.org> >> Sent: Wed, 21 Mar 2012 9:20 >> Subject: Re: [jdev] Problem receiving presence after power outag >> >> On Wed, Mar 21, 2012 at 9:12 AM, Mark Gabriel Paylaga >> <mpayl...@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@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-unsubscr...@jabber.org >> _______________________________________________ >> >> _______________________________________________ >> JDev mailing list >> Info: http://mail.jabber.org/mailman/listinfo/jdev >> Unsubscribe: jdev-unsubscr...@jabber.org >> _______________________________________________ >> >> >
_______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
