Aria Automation Orchestrator fails to run asynchronous workflow started by script when reading from Aria Automation metadata

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• a workflow has been configured as a Day2 item for an Aria Automation deployment
• the workflow script is reading the Aria Automation deployment details, e.g.: System.getContext().getParameter("__metadata_resourceProperties").get("resourceId")
• then another workflow is started asynchronous via the same script e.g.: asyncWorkflow.execute(new Properties())
• the asynchronous workflow was executed however when trying to read from it the web client shows an error and the service restarted after an OutOfMemory exception

Environment

Aria Automation Orchestrator 8.16.2 - 8.18.1

Cause

It appears that some context de/reserialization issue occurs when the asynchronous workflow is started by the same scripting element.

Resolution

VMware is aware of the issue and is working towards a solution.

Workaround:

1. Create two scripting elements - “read properties” and “start workflow”
2. In “read properties” get what is necessary from the __metadata_resourceProperties object and set these values as output parameters of the scripting element
3. In “start workflow” set some input parameters and pass the outputs from the previous script, then call workflow.execute(props) from there.

Before testing the workaround please remove the old tokens to prevent the issue from re-occurring, to do so follow this article:

Selecting Dashboard > Largest token in UI crashes vCO service with 502, OK message