ERROR [ims.tmt.schedule] error executing CronTaskJob java.lang.NullPointerException after Startup Step 27

Document ID : KB000044240
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

The following error appears in the application server log after startup Step 27.

 

[6/20/16 18:40:19:476 EDT] 0000002d SystemOut     O 18:40:19,460 ERROR [ims.tmt.schedule] error executing CronTaskJob

java.lang.NullPointerException

at com.netegrity.ims.businessprocess.InternalServiceAccessor.getManagedObjectProvider(InternalServiceAccessor.java:299)

at com.netegrity.ims.schedule.RecurringTaskJob.execute(RecurringTaskJob.java:58)

at org.quartz.core.JobRunShell.run(JobRunShell.java:199)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)...

 

Solution:

Everything is okay and the error can be ignored. It is simply telling us that the Quartz Scheduler found no environments up and running so it throws a NullPointer. 

Note that the Scheduler starts just prior to the environment startup: 

 

[6/20/16 18:40:19:289 EDT] 00000018 QuartzSchedul I org.quartz.core.QuartzScheduler start Scheduler iam_imDefaultQuartzScheduler_$_NON_CLUSTERED started. 

[6/20/16 18:40:19:289 EDT] 00000018 SystemOut O 18:40:19,289 WARN [ims.default] * Startup Step 27 : Attempting to start environments 

[6/20/16 18:40:19:476 EDT] 0000002d SystemOut O 18:40:19,460 ERROR [ims.tmt.schedule] error executing CronTaskJob 

java.lang.NullPointerException.... 

 

Then immediately after the error, the environments begin to start up, for example: 

 

[6/20/16 18:40:20:194 EDT] 00000018 SystemOut O 18:40:20,178 WARN [ims.tmt.EnvironmentService] * Starting environment: QA_Emp_IME..... 

 

So basically, there is a timing issue which is accounted for in the code to "@return environment object or null if environment does not exist or has not been started." 

The Scheduler checks in frequent intervals for jobs that need to be run so it will be checking for each running environment's OID every time the scheduler check is kicked off. So it follows that there are should be no subsequent null pointer errors once the environments are running. 

Note: If the errors occur after the environments are running please contact CA Support for assistance.