This issue is resolved in VMware Cloud Director 10.4.2 available at Broadcom Downloads.
This issue can be temporarily bypassed by performing a rolling reboot on all cells, or alternatively, by running vmware-vcd services on exclusively the primary cell. For versions 10.4.X, the following configuration changes can be implemented to reduce the impact of this issue. Please note: All cell-management-tool commands listed below only need to be executed on the primary cell
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n "jms.cluster.connectionTTL" -v "90000"
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n "jms.cluster.clientFailureCheckPeriod" -v "45000"
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vc-task-completions-retrieval-timer-interval-sec -v 60
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.activities.activityRelayPollingIntervalMs -v 60000
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n InventoryWait -v 600000
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n event.processor.running.duration.millisec -v 120000
service vmware-vcd restart
To verify if the values are already in place, use the "-l" option in the commands.
Example:
# /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n "jms.cluster.connectionTTL" -l
Property "jms.cluster.connectionTTL" has value "90000
For more information, see the VMware Cloud Director 10.4.2 Release Notes.