org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl$BadTriggerConfigException

All trigger config parsing attempts failed. First reason: [Trigger expression could not be parsed as either a simple period or as a period with an initial offset. Original parse failure: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] did not parse to a long.; nested exception is java.lang.NumberFormatException: For input string: "0,5,10,15,20,25,30,35,40,45,50,55 * * * *"]. To be considered a period with an offset, the expression must match this regexp(without brackets): [^(\d+)/(\d+)$]]. Second reason: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] could not be used to initialize a CronTrigger; nested exception is java.lang.IllegalArgumentException: Cron expression must consist of 6 fields (found 5 in "0,5,10,15,20,25,30,35,40,45,50,55 * * * *")]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Apereo Issues by Jason Elwood, 1 year ago
    All trigger config parsing attempts failed. First reason: [Trigger expression could not be parsed as either a simple period or as a period with an initial offset. Original parse failure: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] did not
  • via Apereo Issues by Jason Elwood, 1 year ago
    All trigger config parsing attempts failed. First reason: [Trigger expression could not be parsed as either a simple period or as a period with an initial offset. Original parse failure: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] did not
  • Stack trace

    • org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl$BadTriggerConfigException: All trigger config parsing attempts failed. First reason: [Trigger expression could not be parsed as either a simple period or as a period with an initial offset. Original parse failure: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] did not parse to a long.; nested exception is java.lang.NumberFormatException: For input string: "0,5,10,15,20,25,30,35,40,45,50,55 * * * *"]. To be considered a period with an offset, the expression must match this regexp(without brackets): [^(\d+)/(\d+)$]]. Second reason: [Config [0,5,10,15,20,25,30,35,40,45,50,55 * * * *] could not be used to initialize a CronTrigger; nested exception is java.lang.IllegalArgumentException: Cron expression must consist of 6 fields (found 5 in "0,5,10,15,20,25,30,35,40,45,50,55 * * * *")] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.parseTriggerConfig(ScheduledTaskWrapperServiceImpl.java:496)[ScheduledTaskWrapperServiceImpl.class:na] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.readNewTriggerConfig(ScheduledTaskWrapperServiceImpl.java:476)[ScheduledTaskWrapperServiceImpl.class:na] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.mergeLatestTriggerConfig(ScheduledTaskWrapperServiceImpl.java:360)[ScheduledTaskWrapperServiceImpl.class:na] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.updateTasks(ScheduledTaskWrapperServiceImpl.java:320)[ScheduledTaskWrapperServiceImpl.class:na] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.updateTasksTask(ScheduledTaskWrapperServiceImpl.java:331)[ScheduledTaskWrapperServiceImpl.class:na] at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl$6.run(ScheduledTaskWrapperServiceImpl.java:274)[ScheduledTaskWrapperServiceImpl$6.class:na] at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE] at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[na:1.7.0_67] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[na:1.7.0_67] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[na:1.7.0_67] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[na:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[na:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[na:1.7.0_67] at java.lang.Thread.run(Thread.java:745)[na:1.7.0_67]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.