Problem Description: qrtz_locks doesn’t exist
Quartz supports data persistence, so if autowire is assembled automatically, create org springframework. scheduling. quartz. The schedulerfactorybean will automatically inject the database datasource into the database, so that quartz will report an error because it thinks it will persist the data.
Solution: whether spring’s default autowire is set to “autodetect” or “byname”, a * QRTZ_LOCKS’ doesn’t exist
Method 1: do not use the default autowire attribute;
Method 2: set autowire = “no” to schedulerfactorybean without changing the spring default autowire attribute.
<bean class="org.springframework.scheduling.quartz.SchedulerFactoryBean" autowire="no">
<property name="triggers">
<list>
<ref bean="simpleTriggerBean" />
</list>
</property>
</bean>
Normally, it will display org quartz.core.Quartzscheduler runs locally, uses memory, and does not support persistence.
Similar Posts:
- How to Solve backend startup error: Quartz scheduler [ruoyischeduler]
- [Solved] expected single matching bean but found 2
- How hibernate 3 used in jbpm4.4 is compatible with spring 5.X and the exception caused by: java.lang.classnotfoundexception: org.hibernate.impl.sessionimpl
- [Solved] intellij IdeaCould not autowire. No beans of xxx
- Springboot starts with @ scheduled and reports an error: no qualifying bean
- Springboot+Elasticsearch Error [How to Solve]
- Cannot resolve reference to bean ‘entityManagerFactory’ while setting constructor argument
- [Solved] Spring introduces the properties variable Error: org.springframework.beans.TypeMismatchException…
- The last packet successfully received from the server was 26,958 milliseconds ago.
- mybatis: Property ‘configuration’ and ‘configLocation’ can not specified with together