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
Server (on Linux) ignores KeepAlive settings, when client connection is lost, the related server connection/process is not killed [CORE6269] #6511
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffreporter: Alexander Peshkov [ alexpeshkoff ] => Alexey Kovyazin [ alexey.kovyazin ] |
Commented by: @AlexPeshkoff That should happen on any linux using systemd (instead init + xinetd). systemd (unlike xinetd) does not provide full control of TCP/IP socket to activated by socket daemon - instead in controls that socket itself. Therefore keep alive should be enabled in it's configuration. PS. No need to frontport to master - we do not start firebird on socket activation since FB4. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.6 [ 10889 ] |
Commented by: @WarmBooter Any chances of having something like this happening on Windows too? From time to time I find "zombie" connections on Windows servers too, with FB 3. |
Commented by: @AlexPeshkoff Definitely linux-specific issue - there is no xinetd or systemd on windows :-) |
Commented by: @WarmBooter Sure, but I was wondering if there is some unknown bug (in Firebird) contributing for the occurrences of zombies on Windows too. |
Modified by: Sean Leyne (seanleyne)description: In a case of abnormal client's disconnect (crash) firebird process on a server hangs forever keeping connection to database open => In a case of abnormal client's disconnect (crash), the server process is not killed, keeping database connection open summary: Firebird ignores KeepAlive settings, when client is lost server process hangs forever => Server (on Linux) ignores KeepAlive settings, when client connection is lost, the related server connection/process is not killed |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @alexeykovyazin
In a case of abnormal client's disconnect (crash), the server process is not killed, keeping database connection open
Commits: e6159c2
The text was updated successfully, but these errors were encountered: