Flag skipIsolationLevelCheck not set on engine configuration init from Webapps

[joaquinfelici]

Environment (Required on creation)

Any

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

When process engine configuration is initialized from the webapps, in the QuerySessionFactory, the skipIsolationLevelCheck flag is not set and therefore not taken into account when initializing the datasource.

Steps to reproduce (Required on creation)

1. Configure Camunda run with property:

camunda:
  bpm:
    generic-properties:
      properties:
        skip-isolation-level-check: true

and with a transaction level different from READ_COMMITED.

2. Start camunda run.
3. On engine initialization, no exception will be thrown because skip-isolation-level-check: true.
4. Open "Admin" webapp and open "Execution Metrics".

Observed Behavior (Required on creation)

An exception will be thrown because the level is not correct and the flag is not set.

Expected behavior (Required on creation)

Same behavior as with engine initialization, the check should be skipped.

Root Cause (Required on prioritization)

The property is not manually retrieved from the config and passed over to the new configuration object here, as done for other properties.

Solution Ideas

Hints

Links

• Ensure database isolation level is correctly set #4516 (comment)

Breakdown

Pull Requests

Preview Give feedback

1. fix(webapps): add skipIsolationLevelCheck to configuration on webapp init #4868
   bot:backport:7.22 ci:all-db +2
   
2. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1342

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[mboskamp]

Looks good. Do we need to backport this fix? The initial feature was delivered for 7.22 as well.

[joaquinfelici]

Thanks @mboskamp, backport PR is merged as well.