View Full Version : sql exception with quartzscheduler using derby

10-01-2007, 12:04 PM
I'm about 95% done with a port of the 1.6RC2 PCI to the Sun Java System Application Server (Glassfish) and using its JavaDB (Derby). Most everything is working with the file based repo. I do get the following SQLException though and would like to ask if someone knows where exactly the query is being built and whether I can tweak the query externally or if it's in java code. Thanks.

16:31:29,347 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
16:31:29,347 INFO [JobStoreTX] Using thread monitor-based data access locking (synchronization).
16:31:30,877 INFO [JobStoreTX] Removed 0 Volatile Trigger(s).
16:31:30,893 INFO [JobStoreTX] Removed 0 Volatile Job(s).
16:31:31,142 INFO [JobStoreTX] JobStoreTX initialized.
16:31:31,142 INFO [StdSchedulerFactory] Quartz scheduler 'PentahoQuartzScheduler' initialized from an externally provided properties instance.
16:31:31,142 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
16:31:31,314 INFO [JobStoreTX] Freed 0 triggers from 'acquired' / 'blocked' state.
16:31:31,330 INFO [JobStoreTX] Recovering 0 jobs that were in-progress at the time of the last shut-down.
16:31:31,330 INFO [JobStoreTX] Recovery complete.
16:31:31,345 INFO [JobStoreTX] Removed 0 'complete' triggers.
16:31:31,345 INFO [JobStoreTX] Removed 0 stale fired job entries.
16:31:31,361 INFO [QuartzScheduler] Scheduler PentahoQuartzScheduler_$_1 started.
org.apache.derby.client.am.SqlException: Syntax error: Encountered "authorization" at line 1, column 21.
at org.apache.derby.client.am.Statement.completeSqlca(Unknown Source)
at org.apache.derby.client.am.Statement.completeExecuteImmediate(Unknown Source)

Running on a WinXP Pro box with JDK

10-02-2007, 03:59 PM
Does Quartz work after this error? Can you run create a schedule?

10-03-2007, 08:35 AM
Thanks for getting back. I can't tell you if Quartz was working or not. After digging (blindly) into the MDR, I happened upon a repository.properties setting late yesterday that suppresses the AUTHORIZATION clause. After some other tweaking, Quartz seems to be working and the Metadata model could be successfully loaded into the CWM database.

# turnoff 'AUTHORIZATION' clause for Derby