We have a screen select list where a person can create a schedule on the fly. In this case the user is validly creating a monthly cron schedule. If they select all days of the month or a large number of them, the cron string ends up being fairly large. Still this is a valid cron format even though it goes over the max 80 characters allowed in Quartz.

Database schema changes are not fun, but increasing the field size here would allow full cron strings to occur. I suggest maybe a size of 120 for a cron expression rather then 80.

Error is below:


ERROR [24042006 11:15:53] - Job Scheduler: Failed to be able to schedule job
with detail=JobDetail '1_jt.15285_js':
jobClass: 'com.expert.MixedJobRunnable isStateful: true
isVolatile: false isDurable: false requestsRecovers: true and
trigger=Trigger '1_jt_tr.15285_js_tr': triggerClass: 'org.quartz.CronTrigger
isVolatile: false calendar: 'null' misfireInstruction: 0 nextFireTime: Mon Apr
24 12:00:00 EDT 2006 <Servlet.Engine.Transports : 1>
(SchedulerRequest.java:307)
org.quartz.JobPersistenceException: Couldn't store trigger: ORA-12899: value
too large for column "EXPERT2"."QRTZ_CRON_TRIGGERS"."CRON_EXPRESSION" (actual:
96, maximum: 80)
 [See nested exception: java.sql.SQLException: ORA-12899: value too large for
column "EXPERT2"."QRTZ_CRON_TRIGGERS"."CRON_EXPRESSION" (actual: 96, maximum:
80)
]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger
(JobStoreSupport.java:964)
at org.quartz.impl.jdbcjobstore.JobStoreTX.storeJobAndTrigger
(JobStoreTX.java:168)
at org.quartz.core.QuartzScheduler.scheduleJob
(QuartzScheduler.java:613)