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

Error reading/writing data to connection [CORE5879] #6137

Closed
firebird-issue-importer opened this issue Jul 26, 2018 · 12 comments
Closed

Error reading/writing data to connection [CORE5879] #6137

firebird-issue-importer opened this issue Jul 26, 2018 · 12 comments

Comments

@firebird-issue-importer

Submitted by: Sorien (sorien)

We are getting random error reading/writing data to/from connection, affecting all our users with servers version 2.5.7, 3.0.2-4 64Bit super server (local and remote servers), errors are mostly random, minutes even seconds after connection is established (there are no keep alive time changes)

at https://merkuris.sk/files/firebirdMK.zip you can find dump obtained from 3.0.4.33011 (64bit) SuperServer running at localhost (Error: -902 error writing data to connection, ~5s after conection established)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Modified by: Sorien (sorien)

description: We are getting random error reading/writing data to/from connection, affecting all our users with servers version 2.5.7, 3.0.2-4 64Bit super server (local and remote servers), errors are mostly random, minutes even seconds after connection is established (there are no keep alive time changes)

at https://merkuris.sk/files/firebirdMK.zip you can find dump optained from 3.0.4.33011 (64bit) SuperServer running at localhost (Error waw: -902 error writing data to connection, ~5s after conection established)

=>

We are getting random error reading/writing data to/from connection, affecting all our users with servers version 2.5.7, 3.0.2-4 64Bit super server (local and remote servers), errors are mostly random, minutes even seconds after connection is established (there are no keep alive time changes)

at https://merkuris.sk/files/firebirdMK.zip you can find dump obtained from 3.0.4.33011 (64bit) SuperServer running at localhost (Error waw: -902 error writing data to connection, ~5s after conection established)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Modified by: Sorien (sorien)

description: We are getting random error reading/writing data to/from connection, affecting all our users with servers version 2.5.7, 3.0.2-4 64Bit super server (local and remote servers), errors are mostly random, minutes even seconds after connection is established (there are no keep alive time changes)

at https://merkuris.sk/files/firebirdMK.zip you can find dump obtained from 3.0.4.33011 (64bit) SuperServer running at localhost (Error waw: -902 error writing data to connection, ~5s after conection established)

=>

We are getting random error reading/writing data to/from connection, affecting all our users with servers version 2.5.7, 3.0.2-4 64Bit super server (local and remote servers), errors are mostly random, minutes even seconds after connection is established (there are no keep alive time changes)

at https://merkuris.sk/files/firebirdMK.zip you can find dump obtained from 3.0.4.33011 (64bit) SuperServer running at localhost (Error: -902 error writing data to connection, ~5s after conection established)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Commented by: @hvlad

The Firebird process is not crashed, you just take a memory dump from live process, correct ?
Any messages in firebird.log ?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Commented by: Sorien (sorien)

yes, firebird.exe did not crash, there is no errors in firebird.log from today

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Commented by: @hvlad

Then i see no sign of problem at Firebird side.
Idle network connection could be broken by intermediate SW\HW entities (such as firewall, switch, etc).

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 26, 2018

Commented by: Sorien (sorien)

problem is that we have like hundreds such reports everyday and our devs see them every day even server and client app are at same machine ... we will investigate more

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 30, 2018

Commented by: Sorien (sorien)

after some investigation it seems to be caused by same server crash reported in CORE5880

dump http://www.merkuris.sk/files/firebird.exe_180730_150924.zip (FB 3.0.4.33011)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 10, 2018

Commented by: @hvlad

Could you test last build from CORE5880 ? It contains some patches that could fix this crash too

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 27, 2018

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2019

Modified by: @pavel-zotov

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

QA Status: No test => Not enough information

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 28, 2020

Commented by: EZEQUIEL COLMANETTI (colmanetti)

This same error occurred to me using version 3.0.5.33220 32bits
with windows 2016 server.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 28, 2020

Commented by: @hvlad

"same error" doesn't means "same reason"

Please, provide additional info, such as crash dump - else there is nothing to look at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants