conductor-oss/conductor

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

Open

#123 aperta il 9 apr 2024

Vedi su GitHub
 (5 commenti) (2 reazioni) (1 assegnatario)Java (894 fork)batch import
bughelp wantedquestion

Metriche repository

Star
 (31.816 star)
Metriche merge PR
 (Merge medio 11g 3h) (43 PR mergiate in 30 g)

Descrizione

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

Guida contributor