Strange DeploymentCache<ProcessDefinitionEntity> usage

[brig1]

Hi,

In DeploymentManager steps for find ProcessDefinitionEntity:
1. get from ProcessDefinitionEntityManager;
2. check in cache and return it from cache.


Maybe first check cache, then select if not found? Or I missed something?

[frederikherema1]

If I remember correctly, selecting is done to make sure another engine on another JVM has deleted the deployment, in case you're running clustered.

[jbarrez]

The first check is actually a light weight check and does not fetch the whole process definition.

As Fred said, the reason why this is done is because of clusterability.