HSQLDB+Quarz using data source causes "Unexpected token: FOR in statement " exception [SPR-6038]

[spring-projects-issues]

steveneo opened SPR-6038 and commented

When system start up, it throw Unexpected token: FOR in statement " exception. More detail at http://forums.opensymphony.com/thread.jspa?threadID=5193&messageID=18002#18002

The configuration looks like:

<bean id="scheduler" class="com.edgenius.wiki.service.impl.SchedulerFactoryBean">
	<property name="applicationContextSchedulerContextKey">
		<value>applicationContext</value>
 		</property>
	<property name="quartzProperties">
		<props>
			<prop key="org.quartz.jobStore.class">org.springframework.scheduling.quartz.LocalDataSourceJobStore</prop>
			<prop key="org.quartz.jobStore.driverDelegateClass">org.quartz.impl.jdbcjobstore.HSQLDBDelegate</prop>
			<prop key="org.quartz.jobStore.tablePrefix">QRTZ_</prop>
		</props>
	</property>
	<property name="dataSource">
		<ref bean="quartzDataSource" />
	</property>
</bean>

---

Affects: 2.5.5

Reference URL: http://forums.opensymphony.com/thread.jspa?threadID=5193&messageID=18002#18002

[spring-projects-issues]

Juergen Hoeller commented

It seems we could detect the use of HSQLDB and automatically deactivate locking in that scenario. We'll try in time for Spring 3.0 RC1.

Juergen

[spring-projects-issues]

Dave Syer commented

I think we can only set the lock manager inside our custom JobStore (LocalDataSourceJobStore), otherwise Quartz will insist that locks are taken if it thinks there is no transaction available (and presumably it always thinks that if we are using Spring). So it won't work with Quartz native data source config but it will work if the user provides a DataSource. The example above should work (but the jobStore.driverDelegateClass and jobStore.class are redundant as far as I can tell).