Details
Description
When an application issues many SendTo services for a TCP socket, a part of the services might be rejected unexpectely with status code with confirmed with status ERR_HIL_OUTOFMEMORY or ERR_SOCK_WOULDBLOCK.
The problem is observed when the number of pending SendTo services exceeds the depth of the internal per socket request queue. For most LFWs this may happen when the Packet Socket Api is configured to accept more than 4 DPM services in parallel. (E.g. via Taglist Setting)
Workaround: For most LFWs the application can avoid the problem by having no more than 4 unconfirmed SendTo services per socket in parallel.
Attachments
Issue Links
- blocks
-
PSPNMV3-857 Upgrade lwIP based IP stack to V5.2.0.8
- Closed
-
PSPNMV3-858 Upgrade lwIP based IP stack to V5.3.0.3
- Closed
-
PSPNSV4-1500 Upgrade lwIP based IP stack to V5.3.0.3
- Closed
-
PSPNSV4-1501 Upgrade lwIP based IP stack to V5.2.0.8
- Closed
-
PSPNSV4-1502 Upgrade lwIP based IP stack to V5.1.0.14
- Closed
-
PSPNSV5-584 Upgrade lwIP based IP stack to V5.2.0.8
- Closed
-
PSPNSV5-585 Upgrade lwIP based IP stack to V5.3.0.3
- Closed
-
PSPNSV5-586 Upgrade lwIP based IP stack to V5.1.0.14
- Closed
- requested by
-
PSPNMV3-856 Packet Socket API may reject SendTo service for TCP socket unexpectedly
- Closed
-
PSPNSV4-1499 Packet Socket API may reject SendTo service for TCP socket unexpectedly
- Closed
-
PSPNSV5-583 Packet Socket API may reject SendTo service for TCP socket unexpectedly
- Closed