Skip to content

Quartz may attempt to use the DataSource before migrations have been run #17528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
zhangxb1987 opened this issue Jul 16, 2019 · 2 comments
Closed

Quartz may attempt to use the DataSource before migrations have been run #17528

zhangxb1987 opened this issue Jul 16, 2019 · 2 comments
Labels
status: superseded An issue that has been superseded by another

Comments

@zhangxb1987
Copy link

zhangxb1987 commented Jul 16, 2019 •
edited by philwebb
Loading

I am trying to use flyway handling the quartz schema initialization, but it seems QuartzAutoConfiguration is always processed ahead of FlywayAutoConfiguration, which will raise the [org.quartz.JobPersistenceException: Couldn't retrieve job: ORA-00942] exception, because the quartz schema is not initialized yet（I am using jdbc as the quartz job store type, spring.quartz.job-store-type=jdbc）.

So, am i got something wrong , or maybe should put

@AutoConfigurationAfter(FlywayAutoConfiguration.class) on the QuartzAutoConfiguration ?

THX!!
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jul 16, 2019
@zhangxb1987
Copy link
Author

Using spring-boot-2.1.6.RELEASE

@wilkinsona wilkinsona changed the title FlywayAutoConfiguration & QuartzAutoConfiguration process order issue Quartz may attempt to use the DataSource before migrations have been run Jul 16, 2019
@wilkinsona wilkinsona added type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged labels Jul 16, 2019
@wilkinsona wilkinsona added this to the 2.1.x milestone Jul 16, 2019
nosan added a commit to nosan/spring-boot that referenced this issue Jul 16, 2019
@nosan
Ensure that that SchedulerFactoryBean} and Scheduler beans depend on the
85a0723 
Flyway and Liquibase.

see spring-projectsgh-17528
@nosan nosan mentioned this issue Jul 16, 2019
Closed
nosan added a commit to nosan/spring-boot that referenced this issue Jul 16, 2019
@nosan
Ensure that SchedulerFactoryBean and Scheduler beans depend on the
1dcbbff 
Flyway and Liquibase.

see spring-projectsgh-17528
nosan added a commit to nosan/spring-boot that referenced this issue Jul 16, 2019
@nosan
Ensure that SchedulerFactoryBean and Scheduler beans depend on the
b5a68f5 
Flyway and Liquibase.

see spring-projectsgh-17528
nosan added a commit to nosan/spring-boot that referenced this issue Jul 17, 2019
@nosan
Ensure that SchedulerFactoryBean and Scheduler beans depend on the
b36c3fc 
Flyway and Liquibase.

see spring-projectsgh-17528
@wilkinsona
Copy link
Member

Closing in favour of #17539.

@wilkinsona wilkinsona removed this from the 2.1.x milestone Jul 17, 2019
@wilkinsona wilkinsona added status: superseded An issue that has been superseded by another and removed type: bug A general bug labels Jul 17, 2019
nosan added a commit to nosan/spring-boot that referenced this issue Jul 17, 2019
@nosan
Ensure that SchedulerFactoryBean and Scheduler beans depend on the
e84b840 
Flyway and Liquibase.

see spring-projectsgh-17528
@snicoll snicoll mentioned this issue Jul 24, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: superseded An issue that has been superseded by another
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wilkinsona @spring-projects-issues @zhangxb1987