Thread: [Jwchat-devel] JWChat timeout/heartbeat issues
Status: Beta
Brought to you by:
zeank
Menu
▾
▴
jwchat-devel
|
From: Liz W. <li...@du...> - 2008-11-26 15:45:43
|
Hi, We are using the following setup: * JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!) * Ejabberd (using its built-in http-bind) * Apache/2.2.9 Things seem to work marvelously, but we see errors every 5 minutes in our Apache log about timeouts: (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1 Looking at the ejabberd and jwchat debug logs we can see JWChat and Ejabberd reconnect after this. Users see no problems. After the 10th reconnect their jabber session fails. At that point JWChat gives up (having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically reconnect. 5 minutes is the amount of time for the Apache Timeout: # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 So it seems that Apache doesn't see any activity on the connection and times it out and ends the connection. My Javascript skills are rather poor, but there seems to be some code in jsjac to do regular "heartbeat" messages, it just is never invoked? How does a BOSH connection indicate that the client is still alive even if no activity is occurring? Thanks for any help, -- Liz Wendland Duke University Office of Information Technology |
|
From: Stefan S. <st...@ze...> - 2008-12-01 11:03:32
|
Hi Liz, please either increase the value for "Timeout" at your apache to sth like 330 or such. Or adjust JSJACHBC_MAX_WAIT at jsjac.js to sth like 280 or such. Cheers, Steve Am 26.11.2008 um 16:45 schrieb Liz Wendland: > Hi, > > We are using the following setup: > * JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!) > * Ejabberd (using its built-in http-bind) > * Apache/2.2.9 > > Things seem to work marvelously, but we see errors every 5 minutes in > our Apache log about timeouts: > > (70007)The timeout specified has expired: proxy: error reading status > line from remote server 127.0.0.1 > > Looking at the ejabberd and jwchat debug logs we can see JWChat and > Ejabberd reconnect after this. Users see no problems. After the 10th > reconnect their jabber session fails. At that point JWChat gives up > (having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically > reconnect. > > 5 minutes is the amount of time for the Apache Timeout: > # > # Timeout: The number of seconds before receives and sends time out. > # > Timeout 300 > > So it seems that Apache doesn't see any activity on the connection and > times it out and ends the connection. > > My Javascript skills are rather poor, but there seems to be some > code in > jsjac to do regular "heartbeat" messages, it just is never invoked? > How > does a BOSH connection indicate that the client is still alive even if > no activity is occurring? > > Thanks for any help, > > -- > Liz Wendland > Duke University Office of Information Technology > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > JWChat-devel mailing list > JWC...@li... > https://lists.sourceforge.net/lists/listinfo/jwchat-devel |
|
From: Liz W. <li...@du...> - 2008-12-02 13:12:01
|
Dear Stefan, You are absolutely right, setting the timeout of the client to less than the apache server solves the problem. In retrospect that seems so obvious. :) Thanks so much for your help and for providing such a terrific application, -- Liz Wendland Duke University Office of Information Technology Stefan Strigler wrote: > Hi Liz, > > please either increase the value for "Timeout" at your apache to sth > like 330 or such. > > Or adjust JSJACHBC_MAX_WAIT at jsjac.js to sth like 280 or such. > > Cheers, Steve > > > Am 26.11.2008 um 16:45 schrieb Liz Wendland: > > >> Hi, >> >> We are using the following setup: >> * JWChat (with latest jsjac lib from SVN - thanks for the ff3 fix!) >> * Ejabberd (using its built-in http-bind) >> * Apache/2.2.9 >> >> Things seem to work marvelously, but we see errors every 5 minutes in >> our Apache log about timeouts: >> >> (70007)The timeout specified has expired: proxy: error reading status >> line from remote server 127.0.0.1 >> >> Looking at the ejabberd and jwchat debug logs we can see JWChat and >> Ejabberd reconnect after this. Users see no problems. After the 10th >> reconnect their jabber session fails. At that point JWChat gives up >> (having exceeded JSJAC_ERR_COUNT = 10) and doesn't automatically >> reconnect. >> >> 5 minutes is the amount of time for the Apache Timeout: >> # >> # Timeout: The number of seconds before receives and sends time out. >> # >> Timeout 300 >> >> So it seems that Apache doesn't see any activity on the connection and >> times it out and ends the connection. >> >> My Javascript skills are rather poor, but there seems to be some >> code in >> jsjac to do regular "heartbeat" messages, it just is never invoked? >> How >> does a BOSH connection indicate that the client is still alive even if >> no activity is occurring? >> >> Thanks for any help, >> >> -- >> Liz Wendland >> Duke University Office of Information Technology >> >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> JWChat-devel mailing list >> JWC...@li... >> https://lists.sourceforge.net/lists/listinfo/jwchat-devel >> > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > JWChat-devel mailing list > JWC...@li... > https://lists.sourceforge.net/lists/listinfo/jwchat-devel > |
Thanks for helping keep SourceForge clean.
X