Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ofbiz.apache.org
Date: Mon, 4 Jan 2016 09:15:39 +0000 (UTC)
From: "Nicolas Malin (JIRA)" <jira@apache.org>
To: dev@ofbiz.apache.org
Message-ID: <JIRA.12924922.1451495242000.7593.1451898939909@Atlassian.JIRA>
In-Reply-To: <JIRA.12924922.1451495242000@Atlassian.JIRA>
References: <JIRA.12924922.1451495242000@Atlassian.JIRA>
 <JIRA.12924922.1451495242522@arcas>
Subject: [jira] [Updated] (OFBIZ-6784) JobSandbox : reload crashed job maybe
 duplicate pending service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nicolas Malin updated OFBIZ-6784:
---------------------------------
    Attachment:     (was: OFBIZ-6784.patch)

> 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
>
> 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)