search

sijugeorge87 / jaxl

Automatically exported from code.google.com/p/jaxl
GNU General Public License v3.0
0 stars 0 forks source link

If talk.google.com or other jabber server don't reply to periodic pings, attempt a reconnect #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Observed with lyricsfly@gtalkbots.com
2. When bot is running for a longer duration, google talk server stops
responding to client ping messages

What is the expected output? What do you see instead?
The bot eventually though seems online, will not receive any xmpp stanza
from the jabber server.

Please use labels and text to provide additional information.
Solution is to try reconnect after a minimum ping request goes unanswered.

Original issue reported on code.google.com by mailsfor...@gmail.com on 15 Jan 2010 at 9:14

GoogleCodeExporter commented 9 years ago 
Hi

Is the latest code in the trunk resolves this issue or i have to handle it 
myself?

Thanks,
Pankaj

Original comment by pankaj.k...@gmail.com on 18 Jan 2010 at 6:23

GoogleCodeExporter commented 9 years ago 
Hi Pankaj,

Expect the code in the trunk by eod today. It's done though not checked in. 
Will do so.

Original comment by mailsfor...@gmail.com on 18 Jan 2010 at 6:41

GoogleCodeExporter commented 9 years ago 
Hi,

I want to know when will you release jaxl-1.0.5 as right now i am able to see 
only
changelog file(r49) in the trunk which displays Version 1.0.5 (In Trunk).
It might resolve my bot disconnectivity issue. 

Thanks,
Pankaj

Original comment by pankaj.k...@gmail.com on 19 Jan 2010 at 6:56

GoogleCodeExporter commented 9 years ago 
Yes Pankaj, a bit of work has been done to solve bot dis-connectivity issue.
Last nail in the coffin will be to attempt auto reconnect in case jabber server 
stop
responding to jaxl pings. I see this happening from gtalk servers every 2-3 
days.

I will checkin the code related to this bug probably by wednesday eod (tight at
office right now). However jaxl-1.0.5 is intended to include BOSH, MUC support 
and
hence official version 1.0.5 might take 2-3 weeks. (Both BOSH, MUC are almost 
ready
for release :D)

Till then you can have code from trunk which should fix your bot 
dis-connectivity issue.

Original comment by mailsfor...@gmail.com on 19 Jan 2010 at 7:01

GoogleCodeExporter commented 9 years ago 
Fixed with Jaxl 2.x

Original comment by mailsfor...@gmail.com on 19 Aug 2010 at 8:49