MisfireHandler: Error handling misfires: Unexpected runtime exception: null org.quartz.JobPersistenceException: Unexpected runtime exception: null

          MisfireHandler: Error handling misfires: Unexpected runtime exception: null
           org.quartz.JobPersistenceException: Unexpected runtime exception: null

Version:-11.1.2.3.0

Error:-

<Feb 19, 2018 4:28:47 PM IST> <Error> <org.quartz.impl.jdbcjobstore.JobStoreCMT> <BEA-000000> <MisfireHandler: Error handling misfires: Unexpected runtime exception: null

org.quartz.JobPersistenceException: Unexpected runtime exception: null [See nested exception: java.lang.NullPointerException]

        at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3042)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)

Caused By: java.lang.NullPointerException

        at org.quartz.SimpleTrigger.computeNumTimesFiredBetween(SimpleTrigger.java:800)

        at org.quartz.SimpleTrigger.updateAfterMisfire(SimpleTrigger.java:514)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStoreSupport.java:944)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:898)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3029)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)

        at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)

CAUSE

Time value.

To Resolve above error from logs:- 

If your using a GTC connector, you need to update the newly created task's "Start date", System Management > Scheduler > *GTCTASK*,

1.      Logon to sysadmin console>schedulers>search for *GTCTASK *>

2.      Change start date time in all GTCTASKS and click on apply

3.      Take backup of tmp, cache and data folder and remove tmp, cache and data folders from all managed server location

4.      Restart Severs

Note: - The default date is 31 Dec 1969, upon being updated with the current date,

                or a date in the future, the exception is gone from the logs.

              (The problem here is that dates prior to UTC midnight 1 Jan 1970 are 

                expressed as negative numbers, and having a negative number as a 

                date causes this exception. Verify that the.Scheduled start times of 

                ALL OIM job instances are set to  sometime after Jan 1, 1970 UTC? Just set

               the start date to post 2000 and after a restart the error should go away.