CS server crash altering SP in 2 connect [CORE210] #538
Assignees
Comments
Modified by: @pcisarassignee: Dmitry Yemanov [ dimitr ] => |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
|
Commented by: Dimitrios Chr. Ioannidis (dchri) Use of the new Target Final Release Version field. |
Modified by: Dimitrios Chr. Ioannidis (dchri)Target Final Release Version: 2.5.0 [ 10221 ] |
Modified by: @pcisarWorkflow: jira [ 10234 ] => Firebird [ 14461 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Open [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] Fix Version: 2.5 Alpha 1 [ 10224 ] => |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
|
Commented by: @pcisar Fix verified, no test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: ded (ded)
SFID: 642411#
Submitted By: ded
If the same procedure is altered on Classic FB1 from
2 connections, undocumented exception "Procedure in
use" is raised or gds_inet crashes. It is depenedent on
transactions parameters. How to reproduce:
Start 2 instances of interactive tool (isql or any
GUI tool) and:
1-st instance
create procedure test
as
begin
exit;
end
Commit
2-nd instance
alter procedure test
as
declare variable a int;
begin
exit;
end
Commit
1-st instance again
alter procedure test
as
begin
exit;
end
Commit
At this point (namely Commit):
if transaction parameters are concurrency wait:
Statement failed, SQLCODE = -902
Error reading data from the connection.
in server log:
Fatal lock manager error: invalid lock id (0) errno: 2
after it if this connection is restarted alter will
be successfull, but if we try alter procedure back in
2-nd (living for this time) instance - it's connection
will be broken too with the same line in log but errno:
4.
Any other parameters of transactions results in
"Procedure in use" message instead of the crash of
gds_inet.
Alexander V.Nevsky.
Commits: c58544e
The text was updated successfully, but these errors were encountered: