Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Extreme slow operations that utilize internal message bus in VMware Cloud Director (78964)

Last Updated: 8/17/2023Categories: TroubleshootingTotal Views: 14868Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

In a VMware Cloud Director multi-cell environment, you experience these symptoms:

If one cell that triggers the task to the vCenter Server and waiting for the task completion notification as part of VCD property collector updates, it ends up waiting for very long time and receive notification only after making a direct call to vCenter Server.

This only happens when you are running with multi-cell. It works fine you are running with single cell or shutdown other cells in case of multi-cell setup.

For example: In the below log snippet, cell02 has trigger the reconfigure task task-50428 and waiting for it completion. Cell01 where Property collector listener is running, has received the task update, just after 4 sec but cell02 never received until cell02 make direct call to VC and received an update.

Task update on cell01
/opt/vmware/vcloud-director/logs/cell-runtime.log.x
2020-04-21 08:48:44,803 | DEBUG    | ActiveMQ Session Task-20  | TaskManager                    | Handling completion update from MessageBusAdapter for task [vcId=<VC_UUID>, moref=task-50428] with state SUCCESS |

2020-04-21 08:48:44,803 | DEBUG    | ActiveMQ Session Task-20  | WaitHandle                     | Task updated. task = [valref = [vcId=<VC_UUID>, moref=task-50428], state = SUCCESS, taskName = ReconfigVM_Task, progress = null, entityName = <VM_NAME>, errorMessage = null], polled from vc = false |

Task status on cell02 by directly polling the VC at around 08:52

2020-04-21 08:48:40,857 | INFO     | net-fabric-activity-pool-198 | VC20VirtualServer              | Invoking reconfigure vm [name = <VM_NAME>, valref = [vcId=<VC_UUID>, moref=vm-8018], changeVersion 2020-04-21T08:43:40.665367Z] for synchronizing nics. | requestId=<REQUEST_UUID>,request=POST https://example.com/api/vdc/<VDC_UUID>/action/composeVApp,requestTime=1587457340266,remoteAddress=<IP>:24200,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 32.0 vcd=<VCD_UUID>,task=<TASK_UUID> activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:<TASK_UUID>) activity=(com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity,urn:uuid:<ACTIVITY_UUID>)
source appname bundle event_type filepath hostname pushed_dt tenant vcd_pr log_message vmw_vcd_severity vmw_vcd_vc_uuid vmw_vcd_uuid

2020-04-21 08:52:01,760 | DEBUG    | VC.TaskManager.TaskCompletionsRetriever | WaitHandle                     | Releasing waiter for task [vcId=<VC_UUID>, moref=task-50428] |

2020-04-21 08:52:01,758 | DEBUG    | VC.TaskManager.TaskCompletionsRetriever | WaitHandle                     | Task updated. task = [valref = [vcId=<VC_UUID>, moref=task-50428], state = SUCCESS, taskName = ReconfigVM_Task, progress = null, entityName = <VM_NAME>, errorMessage = null], polled from vc = true |

You observed ActiveMQ certificate related issue.

You see entries similar to:
/opt/vmware/vcloud-director/logs/cell-runtime.log.x
2020-04-20 14:34:00,520 | ERROR    | ActiveMQ BrokerService[<SERVICE_UUID>] Task-15 | TransportConnector             | Could not accept connection from tcp://<IP>:47990 : javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown |

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs in operation where inter-cell communication is required.
For example: Power on, Power off, compose, instantiate, DFW update, etc and running with multi-cell setup.

The same operation works fine if running with a single cell.

Resolution

To resolve this issue, check if the certificate is expired.

Run this command:

/opt/vmware/vcloud-director/bin/cell-management-tool jms-certificates --status

If yes, regenerate it using this command:

/opt/vmware/vcloud-director/bin/cell-management-tool jms-certificates --certgen --force

Restart all the vCD cells by running this command:

service vmware-vcd restart

Note: If slowness persist even after this, and this exception "SSLHandshakeException: Received fatal alert: certificate_unknown" is no longer visible on the logs, add this parameter using this cell-management-tool and restart all the cells.

vcloud.activities.activityRelayPollingIntervalMs = 5000

Related Information

This Article is not applicable to versions of Cloud Director such as 10.2,  10.3 and 10.4 in which the messaging system has now changed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
将 Cloud Director 9.5 迁移到 10.0 的过程中，出现“无法读取或写入配置文件: 密钥库已被篡改，或密码不正确”错误 (78924)

KB
•
VMware Update Manager の診断情報の収集 (1003693)

KB
•
VMware Intelligent Hub 20.04 for iOS リリースのお知らせ (78889)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

VMware Cloud Director 10.x

Take Our Survey

Support Assistant