Using engine configuration isDbEntityCacheReuseEnabled shows non-transactional behavior #2118
Labels
scope:core-api
Changes to the core API: engine, dmn-engine, feel-engine, REST API, OpenAPI
type:bug
Issues that describe a user-facing bug in the project.
This issue was imported from JIRA:
The configuration option "isDbEntityCacheReuseEnabled" makes the engine share an entity cache between multiple transactions of job execution. However, it also shares it with the transaction that handles the failure of job execution, where the current cache state is not valid anymore, because a previous transaction has been rolled back.
Example:
When the job is executed the first time, the executing transaction fails (due to Task C), however the transaction handling the failed job flushes all the changes made by the previous transaction since it shares the entity cache. This results in:
By default, the option isDbEntityCacheReuseEnabled is set to
false
(which is also the workaround for this problem).related forum post:
https://groups.google.com/forum/?utm*medium=email&utm_source=footer#!msg/camunda-bpm-users/RNS1o7Koi*E/gtklpds7q5wJ
Links:
The text was updated successfully, but these errors were encountered: