Windows client could put 10054 error messages into firebird.log at connection time [CORE3351] #3717
Submitted by: @hvlad
During tests with high load and simultaneous creation of many connections i found that firebriod.log contains a lot of INET errors such as
Debugging shows that in this condition it is possible to have successful call of connect() function followed by error in send() call.
The text was updated successfully, but these errors were encountered:
Commented by: @hvlad
Solution is to use SOMAXCONN as value for backlog parameter at call of listen().
MSDN said about backlog parameter :
Maximum length of the queue of pending connections. If set to SOMAXCONN, the underlying service provider responsible for socket s will set the backlog to a maximum reasonable value.
Note, that SOMAXCONN is still defined as 5 in winsock.h while at winsock2.h it is defined as 0x7fffffff