[Libwebsockets] disconnection after 310 secondes

Peiffer Eric eric.peiffer at al-enterprise.com
Tue Sep 29 14:48:50 CEST 2020


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

level: 8 log: __lws_close_free_wsi: 0x7f66ac00dad0: caller: validity timeout

level: 8 log: __lws_close_free_wsi: shutdown conn: 0x7f66ac00dad0 (sk 26, state 0x119)

level: 16 log: __lws_close_free_wsi: real just_kill_connection: 0x7f66ac00dad0 (sockfd 26)

level: 16 log: _lws_change_pollfd: wsi 0x7f66ac00f350: fd 23 events 1 -> 1

level: 16 log: lwsi_set_state(0x7f66ac00dad0, 0x20000020)

When I search the string "validity too old" in the libwebsockets source code I found in the file : ./core-net/wsi-timeout.c

/* one of either the ping or hangup validity threshold was crossed */

        if (wsi->validity_hup) {
                lwsl_info("%s: wsi %p: validity too old\n", __func__, wsi);
                __lws_close_free_wsi(wsi, LWS_CLOSE_STATUS_NOSTATUS,
                                     "validity timeout");


On what threshold should I act to no longer have disconnection?



De : Peiffer Eric
Envoyé : mardi 29 septembre 2020 14:07
À : libwebsockets at ml.libwebsockets.org <libwebsockets at ml.libwebsockets.org>
Objet : disconnection after 310 secondes


I'm using libwebsockets release v4.1-stable on linux debian 10.
I have implemented a server using libwebsockets 3.2.
Now I have upgraded my application with the release 4.1.
But now for each  client connection, my server received a
LWS_CALLBACK_CLOSED event 310 secondes after the connection.
May be I have forget something like ping/pong configuratio?


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

More information about the Libwebsockets mailing list