[jira] [Updated] (OFBIZ-13370) Recurring Job Not Rescheduled After Server Restart/Crash

["Jacques Le Roux (Jira)" <ji...@apache.org>]

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

Jacques Le Roux updated OFBIZ-13370:
------------------------------------
    Affects Version/s: 24.09.05

> Recurring Job Not Rescheduled After Server Restart/Crash
> --------------------------------------------------------
>
>                 Key: OFBIZ-13370
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13370
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 24.09.05
>            Reporter: Chandan Khandelwal
>            Assignee: Chandan Khandelwal
>            Priority: Major
>
> While reviewing the OFBiz job polling and scheduling process, I noticed a situation where a recurring job may lose its recurrence.
> When a job moves from {{SERVICE_QUEUED}} to {{{}SERVICE_RUNNING{}}}, if the server crashes before the next recurrence job is created, the job remains in {{SERVICE_RUNNING}} state in the database.
> After the server restarts, {{JobManager.reloadCrashedJobs()}} picks up this job and reschedules it. However, it assumes the next recurrence already exists and schedules the job without the {{{}tempExprId{}}}.
> Since the next recurrence was never created due to the crash, the recurrence chain breaks. The job runs once after restart but does not get scheduled again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)