[
https://issues.apache.org/jira/browse/NIFIREG-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356892#comment-16356892
]
Bryan Bende commented on NIFIREG-142:
-------------------------------------
[~doaks80] currently there is a requirement that NiFi Registry be run with a
JDK and not a JRE, this error happens when it is started with a JRE and Flyway
(database migration tool) attempts to use something from the JDK. Can you
confirm if this resolves your problem?
> First start problem: Error creating bean with name 'flywayInitializer'
> ----------------------------------------------------------------------
>
> Key: NIFIREG-142
> URL: https://issues.apache.org/jira/browse/NIFIREG-142
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.1.0
> Environment: RHEL7
> openjdk version "1.8.0_161"
> Reporter: Daniel Oakley
> Priority: Major
>
> Downloaded 0.1.0 tarball and and tried to run on RHEL7. No changes to any
> config files.
> Error in log file was:
> java.lang.RuntimeException:
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'flywayInitializer' defined in class path resource
> [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]:
> Invocation of init method failed; nested exception is
> org.flywaydb.core.api.FlywayException: Validate failed: Detected failed
> migration to version 1.3 (DropBucketItemNameUniqueness)
> I could not find anything about "flyway" in the docs or config files...any
> hints on how to get around this problem?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
