conductor-oss/conductor

[BUG] flyway.postgresql.transactional.lock didn't find in flyway

Open

#123 opened on Apr 9, 2024

View on GitHub
 (5 comments) (2 reactions) (1 assignee)Java (31,816 stars) (894 forks)batch import
bughelp wantedquestion

Description

Describe the bug After getting a new version of conductor, I've got an error while spring boot app is starting.

As far as I researched, flyway does not find prop flyway.postgresql.transactional.lock

Details Conductor version: implementation "org.conductoross:conductor-common:3.18.0" implementation "org.conductoross:conductor-postgres-persistence:3.18.0" implementation "org.conductoross:conductor-core:3.18.0" implementation "org.conductoross:conductor-rest:3.18.0"

To Reproduce Steps to reproduce the behavior:

  1. start Spring boot app
  2. See error in logs: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayForPrimaryDb' defined in class path resource [com/netflix/conductor/postgres/config/PostgresConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.flywaydb.core.Flyway]: Factory method 'flywayForPrimaryDb' threw exception; nested exception is org.flywaydb.core.api.FlywayException: Unknown configuration property: flyway.postgresql.transactional.lock

Expected behavior Spring boot app with conductor runs as expected

Contributor guide