[Libwebsockets] EXT: Re: disconnection after 310 secondes

Peiffer Eric eric.peiffer at al-enterprise.com
Tue Sep 29 17:05:54 CEST 2020


I have put this


efter each LWS_CALLBACK_RECEIVE, and it's work better.

But what I can not anderstand is that, may server connect xmpp client through web socket connections. Each web socket client send to the server
a xmpp ping and the server response to this ping. This for each client and each minutes.
Thean I can not anderstand why this timeout aoccurs, because each minute there data in the both direction.



De : Andy Green <andy at warmcat.com>
Envoyé : mardi 29 septembre 2020 14:57
À : Peiffer Eric <eric.peiffer at al-enterprise.com>; libwebsockets at ml.libwebsockets.org <libwebsockets at ml.libwebsockets.org>
Objet : EXT: Re: [Libwebsockets] disconnection after 310 secondes

** External email - Please consider with caution **

On 9/29/20 1:48 PM, Peiffer Eric wrote:
> Hi,
> I have put libwebsockets trace to the max in order to see  what's happened.
> And just before I receive the LWS_CALLBACK_CLOSED I have the following
> traces:
> level: 8 log: lws_validity_cb: wsi 0x7f66ac00dad0: *validity too old*

If your connections are actually doing stuff in both directions during
this time, you can notify lws using lws_validity_confirmed(wsi) when you
saw something that means the connection must be working in both directions


and it will reset this timeout.

At context / vhost creation time you can set the timeouts


point to a lws_retry_bo_t and set these (in secs)


if you don't, they use the context default which is for ~5min.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20200929/d1680eb0/attachment-0001.htm>

More information about the Libwebsockets mailing list