In version 4.5.x, there have been occurrences where this problem arises because the excessive thread overhead leads to a deadlock, resulting in a timeout in the SDDC GUI and displaying this error. This problem occurs approximately in 60 days interval.
VCF 4.5.x
There is a synchronization block in the code where instances of TopologyNode are used, and multiple threads are contending for access to this block, resulting in a potential bottleneck or deadlock situation. This is occuring due to
current implementation of Lock Manager, whenever any GET call is made to certain resources in inventory, an inventory LOAD event is triggered. This LOAD event is registered by the Topology generator which in turn adds/registers the resource in its cached topology tree. This LOAD event is required by the Topology generator only during the bootstrap of common services. Due to this logic that was added for Lock Manager, every time any GET API call is made to inventory during any workflow, Topology Generator is invoked. This adds additional unecessary overhead to other workflows.
Restart commonsvcs service