BCAAA Debug Log SOCKET_ERROR and ERROR_IO_PENDING

book

Article ID: 167689

calendar_today

Updated On:

Products

CDP Integration Server ProxySG Software - SGOS

Issue/Introduction

When reviewing debug logs for a BCAAA service, you will often see the following entries in the debug log.

2009/07/22 16:56:57.634 [4732] Calling WSARecv len=16405
2009/07/22 16:56:57.634 [4732] WSARecv status=-1 bytes=0 len=16405 lasterror = 0x3e5
2009/07/22 16:56:57.634 [4732] Recv: SOCKET_ERROR=-1
2009/07/22 16:56:57.634 [4732] WSARecv: ERROR_IO_PENDING=0x3e5
2009/07/22 16:56:57.634 [4732] Recv: WaitForMultipleEvents 0x3d43c8=0x17c

What do the SOCKET_ERROR and ERROR_IO_PENDING entries mean ?

 

Resolution

These are side effects of the Windows overlapped I/O API's that BCAAA uses to do socket operations.

These can be safely ignored as they are an expected circumstance of these API returns and do not indicate a failure in the operation of the BCAAA.