Skip to content
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

Random "invalid transaction handle" errors are returned from the engine [CORE5307] #5584

Closed
firebird-automations opened this issue Jul 12, 2016 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Boltik Evgeny (bolt)

Sometimes (almost randomly) DML statement running in a valid transaction context may fail with "invalid transaction handle" error. All subsequent usage of the same transaction handle (including attempt to rollback) raise the same error. The issue manifests itself only when user-defined temporary blobs are involved in DML operations.

Commits: 4759ea8 946c8ef

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

reporter: Dmitry Yemanov [ dimitr ] => Boltik Evgeny [ bolt ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.1 [ 10730 ]

Fix Version: 4.0 Alpha 1 [ 10731 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Not enough information

@firebird-automations
Copy link
Collaborator Author

Commented by: Boltik Evgeny (bolt)

Firebird-3.0.1.32562-0_x64
I tested from 15 to 21 June on the test server.
From 22 June to 3 working servers is no problem.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

Simple test case will be greatly appreciated.

BTW: number of attachments ? FB architecture and other config settings ?

@firebird-automations
Copy link
Collaborator Author

Commented by: Boltik Evgeny (bolt)

Basically the problem was manifested in PHP with pconnect and write blobs. In normal operation, the error appeared rarely and we could not understand why.
Mini test example no.
For playback, I connected the database DY and he caught the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment