vRA7.3 - Calls to vRealize Orchestrator cache

[bdamian]

I've noticed that vRealize Automation 7.3 has a sort of cache for the calls to vRealize Orchestrator.

I have a contextual action that presenta a form with data. This data has an external default value and calls for an Orchestrator Action to get them. But when this values change, vRealize Automation shows the old values for almost a minute. If you select the action a minute later, the correct values are shown.

If I call the action myself in Orchestrator, I always get the updated values.

Is there any way to avoid this vRA cache?

Thanks a lot,

D.

[bdamian]

Another piece of information:

If I call to the vRO action using the o11n-gateway-service, I always see the correct values. So, internally, vRA 7.3 is caching the output of the o11n-gateway-service.

(Ex: POST: /o11n-gateway-service/api/tenants/{tenant}/actions/{actionFolder}/{action}/execute)

Is there any way to deactivate this cache?

D.

[bdamian · Accepted solution]

I finally found the solution to this problem. I'll let the solution here in the case this bothers anyone else:

The cache settings are in the file:

/usr/lib/vcac/server/webapps/advanced-designer-service/WEB-INF/classes/ehcache/asd-ehcache.xml

As you can see there, all Asd modules has a cache of 120 seconds. I've change the Asd_ScriptActionExecutionResult to 10 seconds in the following node:

<cache name="Asd_ScriptActionExecutionResult" eternal="false" maxEntriesLocalHeap="500" overflowToDisk="false"

      diskPersistent="false" timeToIdleSeconds="10" timeToLiveSeconds="10"

      memoryStoreEvictionPolicy="LRU" />

Then you need to restart the services in order to the new configuration takes place.

D.