You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: