Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12114

Spring Boot Starter incorrectly works with multiple databases

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Duplicate
    • L3 - Default
    • None
    • None
    • spring-boot
    • None

    Description

      We're using Camunda BPM with Spring Boot with the following configuration:

      • our primary DataSource bean is our application database
      • we have a non-primary bean camundaBpmDataSource which is the datasource that Camunda should use

      This configuration creates a problem with the DefaultDatasourceConfiguration in the Spring Boot Starter. While the starter expects that Camunda's datasource can be non-default (so camundaBpmDataSource overrides the primary datasource), it uses the default PlatformTransactionManager, which is the transaction manager for the primary datasource.

      As a result, Camunda creates a lot of connections to the primary datasource which it doesn't actually use.

      We've fixed this for ourselves by providing a fixed version of CamundaDatasourceConfiguration, but it would be great if this could be somehow fixed in the starter itself.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            duplicates

            Feature Request - A new feature of the product, which has yet to be developed. CAM-11923 Spring Boot: Pick up a dedicated Camunda transaction manager

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                Unassigned Unassigned
                m_burst Mikhail Burshteyn
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce