Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I am running an HTTPS server (the one under libraries/daemons/HTTP_Server) and after a while of connecting via various devices, I can get it to stop responding to incoming packets. http_server_event_thread_main() waits indefinitely:
result = wiced_rtos_pop_from_queue( &server->event_queue, ¤t_event, WICED_NEVER_TIMEOUT );
However, when I manually call the following, it recovers:
So, the TCP server appears to stop responding for some reason.
Any ideas on what could be responsible for chopping the TCP server off at its knees?
When I restart the server, the log says "No free socket found. Looks like all the sockets are currently in use". It appears that, over time, all sockets on the server get used up and are not freed. If I replace WICED_NEVER_TIMEOUT with a specific time period, and add the following in http_server_event_thread_main(), the streams are disconnected and sockets are re-initialized: