ScriptingJob throws error when result is null

[GoogleCodeExporter]

ScriptingJob throws error when result is null

Original issue reported on code.google.com by saltnlight5 on 23 Oct 2011 at 7:35

[GoogleCodeExporter]

2011-10-23 15:06:00,056 INFO  InMemoryScheduler_Worker-3 
org.quartz.core.JobRunShell:218| Job DEFAULT.LongRunningJob threw a 
JobExecutionException:
org.quartz.JobExecutionException: Failed to execute job DEFAULT.LongRunningJob 
[See nested exception: java.lang.NullPointerException]
        at myschedule.quartz.extra.job.ScriptingJob.execute(ScriptingJob.java:134)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
Caused by: java.lang.NullPointerException
        at myschedule.quartz.extra.job.ScriptingJob.execute(ScriptingJob.java:131)
        ... 2 more

Original comment by saltnlight5 on 23 Oct 2011 at 7:35

[GoogleCodeExporter]

Fixed.

It's caused by a logging statement that could possible be null value.

Original comment by saltnlight5 on 28 Oct 2011 at 2:31

• Changed state: Fixed
• Added labels: Release-2.3.0