org.quartz.SchedulerException: Trigger's name cannot be null

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Terracotta by nh11, 1 year ago
via Terracotta by nh11, 1 year ago
Trigger's related Job's name cannot be null
via Oracle Community by 807596, 1 year ago
Trigger's related Job's name cannot be null
org.quartz.SchedulerException: Trigger's name cannot be null
at org.quartz.Trigger.validate(Trigger.java:945)
at org.quartz.SimpleTrigger.validate(SimpleTrigger.java:965)
at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:825)
at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:254)
at com.motorola.blur.bcms.quartz.CampaignJob.execute(CampaignJob.java:123)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)

Users with the same issue

4 times, 1 year ago

Write tip

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