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

Connection could hung after no activity for 60 seconds [CORE5911] #6169

Closed
firebird-issue-importer opened this issue Sep 14, 2018 · 6 comments

Comments

@firebird-issue-importer

Submitted by: @hvlad

Imagine application that run some query then sleep for 60 seconds then again run query, sleep for 60 sec and so on.

If there are no other connections, or if this is ClassicServer - there could happen a race condition when last (only) worker
thread in network listener exits due to idle timeout (60 sec) and new request is arrived at the same time and left not
processed in queue.
In the case of SS\SC any new request from the other connection will "awake" network server and that request will be
processed, but in the case of CS this is impossible and connection will hung.

The bug is at the thread pool of network listener and can't happen for XNET and WNET protocols which not uses thread pool.

Commits: 7efe280 17bc672

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 14, 2018

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 18, 2018

Commented by: @hvlad

v2.5 seems not affected

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 18, 2018

Modified by: @hvlad

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

Version: 2.5.8 [ 10809 ] =>

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 18, 2018

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 20, 2018

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 20, 2018

Modified by: @pavel-zotov

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

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