ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacopo Cappellato (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-6784) JobSandbox : reload crashed job maybe duplicate pending service
Date Tue, 04 Feb 2020 14:09:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029856#comment-17029856
] 

Jacopo Cappellato commented on OFBIZ-6784:
------------------------------------------

[~nmalin] [~lektran] It would be great if you could have a look at OFBIZ-11340: in it Mohammed
has reported (and proposed a fix for) a regression related to the change in this ticket. You
will find all the details there but essentially the problem is that after this change, if
a job, with temporal expression set, in the QUEUED status is crashed, then the new job created
from it will loose the temporal expression. This is caused by the fact that the temporal expression
is set when new jobs are created for the future and this only happens when the parent job
is moved to RUNNING.

> 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
>            Priority: Major
>              Labels: jobsandbox
>             Fix For: 14.12.01, 12.04.06, 13.07.03, 16.11.01
>
>
> 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
(v8.3.4#803005)

Mime
View raw message