[SERVER-13375] don't rely on ConnectBG thread for nonblocking connect Created: 27/Mar/14  Updated: 28/May/19  Resolved: 28/May/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Greg Studer Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-27240 ConnectBG must not close() while the ... Closed
Related
Participants:

 Description   

We should use a standard nonblocking connect. ConnectBG is particularly fragile when large numbers of connections are created, since it provides poor control over timing and is subject to thread scheduling problems.



 Comments   
Comment by Mira Carey [ 28/May/19 ]

We removed ConnectBG in SERVER-27240

Comment by Greg Studer [ 28/Aug/14 ]

Putting this on hold again - this won't work generically and will require a deeper custom Windows solution:

See:
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/18769abd-fca0-4d3c-9884-1a38ce27ae90/wsapoll-and-nonblocking-connects-to-nonexistent-ports?forum=wsk

Generated at Thu Feb 08 03:31:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.