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

WNET connection locks client if classic listener has stopped [CORE3182] #3556

Open
firebird-automations opened this issue Oct 14, 2010 · 1 comment

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @reevespaul

I was testing the fix for CORE2356 with WNET

This sequence:

o start classic
 o connect isql_client_1 to \\server\db
 o stop classic
 o connect isql_client_2 to \\server\db

leaves the second client connection hanging for what seems like an indeterminate period. (I only waited 20 mins, but that is way too long anyway.)

CORE2356 partially fixes this problem. When the classic listener is restarted the connection completes immediately and successfully.

Servers without the CORE2356 fix (all 1.5, 2.0 and 2.1 prior to 2.1.4) will eventually timeout and return a failed connection attempt to the client but only _after_ the server has restarted.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

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

No branches or pull requests

2 participants