-
-
Notifications
You must be signed in to change notification settings - Fork 233
Long SQL statements break TCP/IP connection [CORE1196] #1621
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
Comments
Commented by: @dyemanov Fixed in CVS a few days ago. |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 1 [ 10141 ] assignee: Vlad Horsun [ hvlad ] |
Commented by: @pmakowski I can't close this one When I run such statement with FB2.1 under Windows with isql, isql crash and I get in firebird.log |
Commented by: @pcisar Can't confirm the fix fox 2.1 Beta 1. Attached script will close the connection and crash the client. It doesn't matter whether the connection is local (firebird.log error is: XNET error (xnet:2044) connection lost: another side is dead) or remote (firebird.log error is: INET/inet_error: read errno = 10054). The server doesn't crash. It works ok in 2.0.1. |
Modified by: @pcisarAttachment: core-1196.sql [ 10470 ] |
Modified by: @pcisarVersion: 2.1 Beta 1 [ 10141 ] Fix Version: 2.1 Beta 2 [ 10190 ] Fix Version: 2.1 Beta 1 [ 10141 ] => |
Modified by: @pcisarsummary: FB 2.1 Alpha 1 - Long SQL statements break TCP/IP connection => Long SQL statements break TCP/IP connection |
Commented by: @hvlad Real reason for bug is not a length of statement text but a big number of output parameters. |
Modified by: @pcisarWorkflow: jira [ 11745 ] => Firebird [ 15536 ] |
Commented by: @pmakowski Q/A test ok |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Submitted by: michalk1 (michalk1)
Is related to QA151
Attachments:
core-1196.sql
Execution of long statement breaks remote protocol connection with errors "Unable to complete network reqest to host" and "Error reading data from the connection" or "Error writing data to the connection". The error probability increases with statement length, especially if it contains comments and/or is spread across many lines.
The same statement executes ok if I
- use true local connection (no localhost) OR
- use stable FB version (2.0.1) OR
- use FB 2.1 Alpha 1, but with older client library (from FB 2.0.1)
This one is long enough to break the connection reliably, but much shorter statements (around 50 lines, 2 kB size) are affected:
SELECT
1, /* Looooooooong comment */
2, /* Looooooooong comment */
....
999, /* Looooooooong comment */
1000
FROM RDB$DATABASE
Commits: 0e50c9f
The text was updated successfully, but these errors were encountered: