New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometime INET error reported as 0 in firebird.log instead of real error code [CORE1276] #1697
Comments
Commented by: @hvlad User report was: INET/select_wait: select failed, errno =0 After it server stop accept new connections but worked well with existing ones |
Modified by: @hvladenvironment: User reported WinXP, FB 2.0.1 but i sure it can happen in every FB version on windows => User reported WinXP, FB 2.0.1 SS but i sure it can happen in every FB SS versions on windows |
Commented by: @hvlad Can't verify fix as i can't reproduce the error |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 1 [ 10141 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @hvladFix Version: 2.0.2 [ 10130 ] |
Modified by: @pcisarWorkflow: jira [ 12171 ] => Firebird [ 15577 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @hvlad
inet.cpp have many places in code when we analyse error code not immediate after sockets function call but after following THREAD_ENTER call.
It seems Win API functions called by THREAD_ENTER (WaitForMultipleObjects for example) can reset error code returned by WSAGetLastError.
Solution is to read WSAGetLastError into local variable immediate after socket function call and operate with this variable not calling WSAGetLastError again
Commits: 337749d 0eb6387
The text was updated successfully, but these errors were encountered: