Looking up a definition by parent deployment id and key (starting a process or case instance with a parent deployment id, the call activity, process task and case task with same deployment, and the BPMN business rule task and CMMN decision task) ran the parent deployment query every time. The id of the found definition is now kept in a cache per parent deployment (or deployment) and key, so a hit no longer runs that query.

• Process definitions: a cached id is checked by selecting the definition by id.
• Case definitions and decisions: by default a cached id is checked by selecting the definition by id, so a definition that was undeployed on another node is detected. With verifyCachedSameDeploymentDefinitions disabled on the CMMN or DMN engine configuration, the definition is taken from the definition cache without a select.
• Misses of the parent deployment lookup are only cached when the new cacheSameDeploymentDefinitionMisses is enabled (disabled by default), because in a cluster a node that did not do the deployment would keep the miss when a new child deployment is added under an existing parent. Misses of the call activity lookup are always cached.
• A cached miss applies to the tenant it was recorded for.
• Deploying and removing a deployment evicts the entries of its definition keys.
• The cache uses the definition cache limit of the engine and can be replaced through setSameDeploymentDefinitionCache.

The last commit fixes the ProfilingDbSqlSessionFactory used by the database operation count tests. DbIdGenerator fetches a new id block through the process engine command executor, so when a command of another engine was profiled, the next.dbid select was counted for that command whenever the id block ran out during it.

Check List:

• Unit tests: YES
• Documentation: NA