UDT Reference: Error Codes |
All UDT API will return an error upon a failed operation. Particularly, UDT defines UDT::INVALID_SOCK and UDT::ERROR as error returned values. (several routines return false as error value.) Application should check the return value against these two constants.
Error Code | Comment |
---|---|
0 |
success operation. |
1000 |
connection setup failure. |
1001 |
server does not exist. |
1002 |
connection request was rejected by server. |
1003 | could not create/configure UDP socket. |
1004 | connection request was aborted due to security reasons. |
2000 | connection failure. |
2001 |
connection was broken. |
2002 |
connection does not exist. |
3000 |
system resource failure. |
3001 | could not create new threads. |
3002 | could not allocate memory buffers. |
4000 |
file access error. |
4001 |
file access error, invalid read offset. |
4002 |
file access error, do not have read privilege. |
4003 |
file access error, invalid write offset. |
4004 |
file access error, do not have write privilege. |
5000 |
operation not supported. |
5001 |
cannot execute the operation on bound socket. |
5002 |
cannot execute the operation on connected socket. |
5003 |
bad parameters. |
5004 |
invalid UDT socket descriptor. |
5005 |
cannot listen on unbound socket. |
5006 |
(accept) socket is not in listening state. |
5007 | rendezvous connect process does not allow listen and accept call. |
5008 | the rendezvous set up processing is enabled; bind should be called before connect. |
5009 | operation not supported in SOCK_STREAM mode. |
5010 | operation not supported in SOCK_DGRAM mode. |
6000 |
non-blocking call failure. |
6001 |
no buffer available for sending. |
6002 |
no data available for reading. |
6003 | no buffer available for the non-blocking recv call. |
6004 |
an overlapped recv is in progress. |