Certain finder functions within vRealize Orchestrator 7.4+ cause unresponsiveness, out of memory errors and/or heap dumps in larger environments
search cancel

Certain finder functions within vRealize Orchestrator 7.4+ cause unresponsiveness, out of memory errors and/or heap dumps in larger environments

book

Article ID: 326097

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • vRealize Orchestrator (vRO) appears unresponsive.
  • Memory consumption on the appliance is very large.
    • Potential Java out of memory (OOM) crashes may occur within the vRO service.


Environment

VMware vRealize Automation 7.6.x
VMware vRealize Automation 7.5.x
VMware vRealize Automation 7.4.x

Cause

Workflows or scripted actions leveraging the below finder functions in larger environments loads all vRealize Automation objects of the desired type with all their associated data.
  • Server.findAllForType()
  • vCACCAFEntitiesFinder.getXXX
  • vCACCAFEntitiesFinder.findXXX
If 10 workflows are running at the same time, these objects will be loaded 10 times consuming a significant amount of memory.

Resolution

Avoid these functions.  Utilize OData queries with filters to retrieve the desired objects.

See Usage of Odata Filtering for Catalog API for further details on examples.

Additional Information

https://vdc-download.vmware.com/vmwb-repository/dcr-public/d2e4e058-df27-4ac1-a100-4dfd0ef774c0/cb3a080c-8e25-4492-9f1e-ff923ec1b98c/tips.html#pagination
https://github.com/vmware-samples/vra-api-samples-for-postman/tree/master/API%20Tips

Powered by Wolken Software