Hi folks,
I have been working with mod_ping lately.
I came across this:
ping_interval: Seconds
How often to send pings to connected clients, if the previous option is enabled. If a client connection does not send or receive any stanza in this interval, a ping request is sent to the client. The default value is 60 seconds.
timeout_action: none|kill
What to do when a client does not answer to a server ping request in less than 32 seconds. The default is to do nothing.I wish to know if there's a way possible to change the 32 seconds interval to a smaller value?
I would like to change it at the ejabberd level.
As an alternative, i can change it at the Linux OS level for the TCP keep-alive mechanism. Would changing that work in this scenario?
Thanks
Regards
methamphetamine wrote: I wish
I wish to know if there's a way possible to change the 32 seconds interval to a smaller value?
I would like to change it at the ejabberd level.
I think that value is defined in ejabberd_local.erl You would need to modify this line, and recompile the module:
OKay. Thanks for the
OKay. Thanks for the info.
Curious to know if changing this parameter will have any impact on the overall functionality of the ejabberd.
I know the sockets will get closed earlier. Any other impact you could tell?
Hi We modified this value to
Hi
We modified this value to 8 seconds and have been testing it out for quite some time now. We haven't faced any more issue due to this parameter but sometimes we have seen that the connections between client and server gets reset without any network fluctuations so may be this 8 seconds is quite a less timer. We are still debugging and will update if anything comes up due to this parameter.
regards,
Kunal