Spring Boot Starter incorrectly works with multiple databases

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Duplicate
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: spring-boot
    • None

      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.

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: