Indexing Job Scheduling
From DBSight Full-Text Search Engine/Platform Wiki
|Table of contents|
Why my scheduled job didn't start?
There of course can be several reasons.
Wrong Java version
During indexing, DBSight will try to use the java that's available on the path. Sometimes, a machine can have several versions of Java installed, and DBSight could be using one that's lower than java 1.5.
To fix this, make sure the path has the right Java version, and start the application server from the shell(command line mode) with the correct path.
Too crowded jobs
- By default, there is only one indexing job at any point of time.
- By default, there is only 60 seconds mis-fire threshold.
So it means if two jobs are scheduled to start at the same time, and the first one is taking more than 60 seconds, the second one will not be started.
The misfire threshold of 60 seconds is set in file
WEB-INF/conf/quartz.properties org.quartz.jobStore.misfireThreshold = 60000
To fix this, you can modify threshold, or assign jobs to different time slots.