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 * * * *")]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

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
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)
at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.readNewTriggerConfig(ScheduledTaskWrapperServiceImpl.java:476)
at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.mergeLatestTriggerConfig(ScheduledTaskWrapperServiceImpl.java:360)
at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.updateTasks(ScheduledTaskWrapperServiceImpl.java:320)
at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl.updateTasksTask(ScheduledTaskWrapperServiceImpl.java:331)
at org.jasig.ssp.service.impl.ScheduledTaskWrapperServiceImpl$6.run(ScheduledTaskWrapperServiceImpl.java:274)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.