ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-11340) Crashed Scheduled jobs are not getting rescheduled with temporal expression
Date Thu, 06 Feb 2020 16:17:00 GMT

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

ASF subversion and git services commented on OFBIZ-11340:
---------------------------------------------------------

Commit 47e689b360f370bba4f512c314879711aee3d96d in ofbiz-framework's branch refs/heads/trunk
from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=47e689b ]

Fixed: Crashed Scheduled jobs are not getting rescheduled with temporal expression
(OFBIZ-11340)

When a OFBiz server are stopped or crashed with job on queued state,
at the start, they are restarted but without information on tempExprId and recurrenceInfoId

This causes a break for recurrence jobs to their planning

Thanks to Mohammed Rehan Khan for this issue and Scott Gray for the review.


> Crashed Scheduled jobs are not getting rescheduled with temporal expression
> ---------------------------------------------------------------------------
>
>                 Key: OFBIZ-11340
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11340
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Mohammed Rehan Khan
>            Assignee: Nicolas Malin
>            Priority: Major
>         Attachments: OFBIZ-11340.patch, OFBIZ-11340.patch, OFBiz_ JobSandbox_1.png, OFBiz_
JobSandbox_2.png
>
>
> *Scenario:*
>  # Import Schedule service data with temporal expression id.
>  # JobManager creates a child Job with temExprId in _pending_ status when the imported
Job is in _running_ status.
>  # Now the parent Job is in _running_ status and the child Job, which is in _pending_ status,
transitions to _queued_ status if Job Poll size is full. In this scenario, if we restart
the server then both Jobs are Crashed and JobManager creates child Job without tempExprdId. 
>  
>  *Example:* Please refer to the attached screenshots.
>  # Job 32993100 is imported with TempExprId
>  # When Job 32993100 is in running status, then Job 32993101 is created with TempExprId
in pending status but job 32993101 is moved to Queued status if job poll size is full.
>  # If we restart the server then JobPoller runs reloadCrashedJobs() and both jobs are
crashed and JobManager creates two child jobs (32993200, 32993201) without TempExprId.
> So in this case of missing temporal expression id job manager will not be able to schedule further
jobs.
>   
>  *Expected:* If Queued Job (32993101) is crashed then its corresponding Job (32993200)
should have TempExprId to continue further scheduling. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message