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
Incorrect commit instead of rollback during shutdown [CORE118] #440
Comments
Commented by: Alice F. Bird (firebirds) Date: 2005-04-26 17:48 Confirmed, thank you very much. Will be fixed ASAP. |
Commented by: Alice F. Bird (firebirds) Date: 2005-04-26 11:38 Enclosed you will find a simulator of described bug. Other Martin |
Commented by: Alice F. Bird (firebirds) Date: 2005-04-26 00:09 A test case is required. Such things should never happen. |
Commented by: @pcisar Reopened just to add attachment. |
Modified by: @pcisarstatus: Closed [ 6 ] => Reopened [ 4 ] SF_ID: 1155183 => resolution: Fixed [ 1 ] => |
Commented by: @pcisar Source of simulator tool (exe exeeds the limit 256kb of attached file - I will send it by request) |
Modified by: @pcisarAttachment: FB_commit_test.zip [ 10039 ] |
Modified by: @pcisarstatus: Reopened [ 4 ] => Closed [ 6 ] resolution: Fixed [ 1 ] SF_ID: 1155183 => |
Modified by: @pcisarWorkflow: jira [ 10142 ] => Firebird [ 14354 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: mjanus (mjanus)
Attachments:
FB_commit_test.zip
SFID: 1155183#
Submitted By: mjanus
Hi,
I've found some incorrect behavior of Firebird
SuperServer 1.5.1 (tested on WinXP SP2 or MS
SBS2003 or Win2K).
If I make shutdown of FB server during one active
transaction I would expect that all active transactions
will be rolled back. However, I've found that some part of
changes in such a transaction are curiously committed.
For example: If I make a loop of inserting new records
into some table and during this transaction I make the
shutdown, the client app is terminated by connection
lost as is expected but the server will committed a lot of
inserted records - sometimes the server commits last 5
pcs of hunderds of inserted records, at another time the
server saved all records except last 7pcs etc.
PS: I know that I must check if there is no active
transaction prior to making shutdown but I think this is
an unpleasant and serious bug.
Martin Janus
The text was updated successfully, but these errors were encountered: