-
Notifications
You must be signed in to change notification settings - Fork 90
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.
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
2.0.5 did not start due to missed tables #55
Comments
This is double of #50. I am already propose the pull request, I am don't undestend why owner does not apply it. I think your debug problem linked with this, maybe you better play with 2.0.1, as i see by commits between them is not a big difference. |
Alex, thanks. But do you have sql script for creating all need db layout? I want to launch 2.0.5 anyway, so need to create layout manually. |
https://quartz-scheduler.org/downloads, Docs\DBTables in archive |
+1 on this issue |
we can't auto create the tables, the proper schema needs to be applied for On Tue, Feb 16, 2016 at 1:33 PM, tolyo notifications@github.com wrote:
|
Please publish the version 2.0.6 , my patch already in it. Otherwise ramstore is not working with hibernate. |
2.0.6 has published from bug #50 - however the plugin will not create tables for you, as I said you have to use the DDL supplied with quartz distro for your particular database. |
I try to use 2.0.5 and if fails by default:
org.springframework.context.ApplicationContextException: Failed to start bean 'quartzScheduler'; nested exception is org.springframework.scheduling.SchedulingException: Could not start Quartz Scheduler; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Table 'localShema.QRTZ_LOCKS' doesn't exist [See nested exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'localShema.QRTZ_LOCKS' doesn't exist]
It needs some database layout, but did not create it by itself, also I can not find any sql script to create all needed db stuff.
The text was updated successfully, but these errors were encountered: