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
Transactions with isc_tpb_autocommit can hang the server [CORE4840] #5136
Comments
Modified by: @mrotteveelAttachment: TpbAutocommitTest.java [ 12766 ] |
Modified by: @mrotteveeldescription: I was testing the pull request of Maxim for Jaybird. A test that creates a stored procedure and adds a comment on that stored procedure in a transaction with isc_tpb_autocommit hangs the entire Firebird 3 server. The Firebird 3 server stops responding entirely. The test is (see also attachment):
The same test runs fine against Firebird 2.5.4. The firebird.log contains: RAMONA Sun Jun 14 10:56:16 2015 RAMONA Sun Jun 14 10:56:16 2015 => I was testing the pull request of Maxim for Jaybird. A test that creates a stored procedure and adds a comment on that stored procedure in a transaction with isc_tpb_autocommit hangs the entire Firebird 3 server. The Firebird 3 server stops responding entirely. The test that reproduce this is (see also attachment):
The same test runs fine against Firebird 2.5.4. The firebird.log contains: RAMONA Sun Jun 14 10:56:16 2015 RAMONA Sun Jun 14 10:56:16 2015 |
Modified by: @mrotteveeldescription: I was testing the pull request of Maxim for Jaybird. A test that creates a stored procedure and adds a comment on that stored procedure in a transaction with isc_tpb_autocommit hangs the entire Firebird 3 server. The Firebird 3 server stops responding entirely. The test that reproduce this is (see also attachment):
The same test runs fine against Firebird 2.5.4. The firebird.log contains: RAMONA Sun Jun 14 10:56:16 2015 RAMONA Sun Jun 14 10:56:16 2015 => I was testing the pull request of Maxim for Jaybird. A test that creates a stored procedure and adds a comment on that stored procedure in a transaction with isc_tpb_autocommit hangs the entire Firebird 3 server when executing the statement that adds the comment. The Firebird 3 server stops responding entirely. The test that reproduce this is (see also attachment):
The same test runs fine against Firebird 2.5.4. The firebird.log contains: RAMONA Sun Jun 14 10:56:16 2015 RAMONA Sun Jun 14 10:56:16 2015 |
Modified by: @dyemanovFix Version: 3.0 RC 1 [ 10584 ] |
Commented by: @mrotteveel BTW: This looks a lot like CORE3825 |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully Test Details: Confirmed: |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] Test Details: Confirmed: => Confirmed: |
Submitted by: @mrotteveel
Attachments:
TpbAutocommitTest.java
I was testing the pull request of Maxim for Jaybird. A test that creates a stored procedure and adds a comment on that stored procedure in a transaction with isc_tpb_autocommit hangs the entire Firebird 3 server when executing the statement that adds the comment. The Firebird 3 server stops responding entirely.
The test that reproduce this is (see also attachment):
The same test runs fine against Firebird 2.5.4.
The firebird.log contains:
RAMONA Sun Jun 14 10:56:16 2015
Database: D:\DEVELOPMENT\PROJECT\JAYBIRD\JAYBIRD\FBTEST.FDB
internal Firebird consistency check (Too many savepoints (287), file: tra.cpp line: 2470)
RAMONA Sun Jun 14 10:56:16 2015
Database: D:\DEVELOPMENT\PROJECT\JAYBIRD\JAYBIRD\FBTEST.FDB
internal Firebird consistency check (Too many savepoints (287), file: tra.cpp line: 2470)
internal Firebird consistency check (wrong record version (185), file: vio.cpp line: 3740)
Commits: 302cd6b FirebirdSQL/fbt-repository@cfcc21e
====== Test Details ======
Confirmed:
1. Crash on LI-V3.0.0.32173, WI-V3.0.0.32239 Rev: 62703 (nightly update)
2. Normal work on LI-V3.0.0.32239 Rev: 62705
The text was updated successfully, but these errors were encountered: