[jira] [Updated] (OFBIZ-6784) JobSandbox : reload crashed job maybe duplicate pending service

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux updated OFBIZ-6784:
-----------------------------------
    Fix Version/s: Trunk

> JobSandbox : reload crashed job maybe duplicate pending service
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-6784
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6784
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Nicolas Malin
>            Assignee: Nicolas Malin
>              Labels: jobsandbox
>             Fix For: Trunk, 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
>
>
> 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

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)