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

Server may stop responding to a particular client attachment under some conditions [CORE2742] #3137

Closed
firebird-automations opened this issue Nov 8, 2009 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

It seems there's a small time frame when the remote server may ignore the just received incoming operation request, thus blocking the client application (which is synchronously waiting for a reply packet). The listener thread is still operational in this case.

It's really hard to reproduce, the only known condition is that the client application should send packets with an interval of 60 seconds which corresponds to a timeout to shutdown the inactive worker thread. Reported against Classic, but SuperServer may also be affected.

Commits: 25957ce c122909

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

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