[SERVER-51080] Reorder networking init in mongobridge Created: 21/Sep/20  Updated: 24/Nov/20  Resolved: 24/Nov/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52819 Always initialize TransportLayer and ... Closed
Sprint: Service arch 2020-10-05, Service arch 2020-11-02, Service arch 2020-11-16, Service arch 2020-11-30
Participants:

 Description   

mongobridge creates the ServiceEntryPoint before the TransportLayer here. This is the right order for the startup but not the creation since the ServiceEntryPoint must reference the TransportLayer during startup.



 Comments   
Comment by Githook User [ 22/Sep/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-51080 Fix mongobridge startup ordering
Branch: fixed_thread_pool_handshaking
https://github.com/mongodb/mongo/commit/efb3f7689e9f6c54f039dab068c4c279cf87ac99

Generated at Thu Feb 08 05:24:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.