[SERVER-82674] Multiple TransportLayers exist Created: 01/Nov/23  Updated: 14/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Sprint: Service Arch Prioritized List
Participants:

 Description   

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.


Generated at Thu Feb 08 06:49:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.