[Jwchat-devel] JWChat timeout/heartbeat issues

[Liz W. <li...@du...>]

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