[EMAIL PROTECTED] wrote:
DirectSchedulerFactory.getInstance().createScheduler(DEFAULT_QUARTZ_SCHEDULER_NAME + runID, runID, pool, store);
IMHO, it should cause problem with JDBC job store, and with clustered Cocoon servers also. Point of JDBC store is to coordinate cron jobs between several Cocoon instances.
... or may be not. Have you used quartz + jdbc store configuration?
Vadim
