Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82674

Multiple TransportLayers exist

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Fully Compatible
    • Networking & Obs 2024-07-08, Networking & Obs 2024-09-30, Networking & Obs 2024-10-14, Networking & Obs 2024-10-28, Networking & Obs 2024-11-11
    • 0

      makeNetworkInterface does not accept a ServiceContext*. When called, it will acquire a pointer to the global service context should a global context exist. If makeNetworkInterface cannot acquire a global context, such as if it is invoked before the global service context is installed, it will construct a NetworkInterfaceTL with a NULL ServiceContext. When this happens, NetworkInterfaceTL will construct its own owned TransportLayer.

      This means that every ThreadPoolTaskExecutor made in a decoration's default constructor or in a ServiceContext::ConstructorActionRegisterer will possess its own TransportLayer.

            Assignee:
            joseph.prince@mongodb.com Joseph Prince
            Reporter:
            spencer.jackson@mongodb.com Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: