-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: quarkus
-
None
AT
The engine uses a data source configured via Quarkus Agroal persistence layer:
- Quarkus Agroal provides a transaction manager which allows users to integrate with their Quarkus application into process engine transactions
- The transaction manager should be used by the process engine
- Root cause the exception thrown when configuring the transaction manager with H2 => See the missing enlisted connection support
- When not other configured, the default datasource is configured as an on-disk h2 database to provide a good getting started experience
- When multiple datasources are available, it is possible to configure the extension to use a datasource by name via quarkus.camunda.bpm.datasource=my-datasource-name property
- When the property is not defined, the default datasource is used