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
Firebird hangs for a while blocking all DB operations periodically. [CORE3857] #4197
Comments
Commented by: Sean Leyne (seanleyne) This issue should be handled/directed to the Firebird Support mailing list, this is a support issue. This tracker is NOT a support tool, it is intended for only confirmed problems. |
Commented by: anthony jang (anthonyjang) Firebird mini-dump and lock-print during the blocking. Vlad mentioned that he would look at it. |
Modified by: anthony jang (anthonyjang)Attachment: fb_inet_server_minidump.zip [ 12167 ] |
Commented by: Jesus Angel Garcia Zarco (cointec) I'm having the same issue on a Windows 2008 server R2 64 bits and 16 Gb RAM. |
Commented by: Jesus Angel Garcia Zarco (cointec) Hello Anthony, have You discovered something about this issue? |
Commented by: anthony jang (anthonyjang) This problem occurred again this morning. Attached is the Firebird dump file. Vlad has been emailed the dump files as well. |
Modified by: anthony jang (anthonyjang)Attachment: fb_inet_server_081012.zip [ 12191 ] |
Commented by: anthony jang (anthonyjang) Jesus, We do not have a solution to this issue yet. New dump files have been attached that may help to resolve the issue. |
Commented by: Sascha Michel (datiscum1) Do you use the firebird event mechanism on the Server ? |
Commented by: Sascha Michel (datiscum1) I think that's the same as: CORE4680 Behave exactly the same thing I have described! If the causative client process is aborted, the server running as if there was no problem. The problem occurs unfortunately only very rarely. I watch the problem for more than 10 years and unfortunately it still exists in Firebird 3.0. I have a workaround for the problem and since this on the same system i had no more problems with that bug. My workaround works like this: I think that network sockets are closed by the immediate killing of the program and the server can therefore take up its work again. I very much hope, that at some point the real problem is found in the server, but that no longer interests me so much. |
Commented by: Siva Ramanathan (s2ramana) We have not seen this problem in the latest Firebird release, 2.5.4, so we believe that it has been resolved. We were not using Firebird events. |
Commented by: Sean Leyne (seanleyne) Have you tested the latest v2.5.x and/or v3.0 Beta 2 releases? |
Commented by: Sascha Michel (datiscum1) I have now again tested it with version "LI-V6.3.0.31936 Firebird 3.0 Release Candidate 1". There are differences from the previous version. 1. The error occurs faster. Here entries from the log file: TEST1 !! FB30 Thu Jul 16 11:10:53 2015 ---------------------------------------------------------------------------------------------------- |
Commented by: Veselin Pavlov (pavlov_v) I am experiencing this problem also. Most of the time is early in the morning while first users are connecting. Server Version: LI-V2.5.6.27008 Firebird 2.5 At active time we have: On application login there are a lot of events registering. |
Commented by: Han (h0bby) I am experiencing the same problem My workaround works like this: help is greatly appreciated.. |
Commented by: @hvlad a) make sure you use latest Firebird release |
Commented by: Sascha Michel (datiscum1) For Windows, the thread that is started makes nothing other than terminate the application hard. void __fastcall TKillTimerThread::Execute() |
Submitted by: anthony jang (anthonyjang)
Attachments:
fb_inet_server_minidump.zip
fb_inet_server_081012.zip
Votes: 4
We have a Firebird server installation that periodically blocks all operations for a few minutes and then comes back alive on its own. This has happened about once a month for the last few months. During this blocking period, Firebird CPU usage is unusually low as this is a busy server. This server normally has 200-300 client attachments. The blocking time has varied from 2 minutes to over 10 minutes. During this time, no Firebird operations can be performed i.e. New connections are blocked along with existing connections. Upon recovery, Firebird continues processing without any other issues.
We have noticed that this has generally occurred, but not always, during a DB sweep. Our sweep interval is set to 0 and we are performing the sweep once a day as a scheduled task.
The text was updated successfully, but these errors were encountered: