You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the wss_server example after connecting a client, disconnecting and reconnecting it ~10 times the next reconnect fails. It seams as if every connection uses a new socket and once the default max_clients are reached no new connections are possible.
Expected Behavior
The sockets' storage would be marked as unused after it got closed/disconnected so it can be reused.
Since lru_purge_enable is true in the example I thought the least recently used socket would be reused anyway.
Actual Behavior
W (129257) httpd: httpd_accept_conn: error in accept (23)
indicates that all possible storage for 10 simultanious clients is used up even though no client is connected and only one tryes to connect
Steps to reproduce
Run the wss_server example
connect a client
disconnet the client
reconnect the client
repet 3. and 4. untill the reconnect fails (around 10 connects in total)
I attatched an html file that I run in my browser to connect to the wss_server in the broser you can type in the IP the esp gets from your router.
Code to reproduce this issue
wss_server example
Debug Logs
...
I (115957) wss_echo_server: New client connected 62
I (115967) wss_echo_server: Handshake done, the new connection was opened
I (118987) wss_echo_server: frame len is 0
I (118997) wss_echo_server: Client disconnected 62
I (123417) wss_echo_server: New client connected 63
I (123437) wss_echo_server: Handshake done, the new connection was opened
I (125647) wss_echo_server: Active client (fd=63) -> sending async message
I (125787) wss_echo_server: frame len is 0
I (125787) wss_echo_server: Client disconnected 63
W (129257) httpd: httpd_accept_conn: error in accept (23)
W (129257) httpd: httpd_server: error accepting new connection
github-actionsbot
changed the title
Wss_server example no longer accepts new connections after several reconnects
Wss_server example no longer accepts new connections after several reconnects (IDFGH-7609)
Jun 15, 2022
Thanks for this incredibly fast response.
Works absolutly fine.
I'm more than happy with that solution but shoudn't lru_purge_enable have jumped in or am I misinterpreting how that is supposed to work?
Environment
Problem Description
When running the wss_server example after connecting a client, disconnecting and reconnecting it ~10 times the next reconnect fails. It seams as if every connection uses a new socket and once the default
max_clients
are reached no new connections are possible.Expected Behavior
lru_purge_enable
is true in the example I thought the least recently used socket would be reused anyway.Actual Behavior
indicates that all possible storage for 10 simultanious clients is used up even though no client is connected and only one tryes to connect
Steps to reproduce
I attatched an html file that I run in my browser to connect to the wss_server in the broser you can type in the IP the esp gets from your router.
Code to reproduce this issue
wss_server example
Debug Logs
Note: I removed my credentials from the sdkconfig
test_client.zip
sdkconfig.zip
The text was updated successfully, but these errors were encountered: