Right now the HTTP/Netconn code is replaced with TCP/IP echo server using the sockets API. It 's the typical architecture of a listener thread that spawns connection-handler threads. When we exercise more than one simultaneous connection, there are some glitches -- timeouts and hangs. A sample of a robust multi-connection TCP/AP application using ST's LwIP+FreeRTOPs will be helpful. Thanks.