When the JobPoller run reloadCrashedJobs() after an OFBiz restart, if you have a large service that crash that already replenish the pool receive a new run instant for it.
Example: If you have a service like loadExternalOrder that run each hours. You stop your OFBiz during their activity and at restart you have :
- job1 loadExternalOrder RUNINNG
- job2 loadExternalOrder PENDING at t+1h (normal schedule)
- job1.1 loadExternalOrder PENDING at t+1h (crashed schedule)
I propose to exclude from the process reloadCrashedJobs() all jobs that have already a new scheduled instance