Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Failed JobExecution due to unavailable TaskExecutor leaves End Time unpopulated [BATCH-2760] #844
While executing SimpleJobLauncher#run() assuming that the taskExecutor cannot pick up the submitted Job Execution then a TaskRejectedException will be thrown setting the Job Execution's status to FAILED
On the other hand when querying the JobExplorer via SimpleJobExplorer#findRunningJobExecutions() for running Job Executions the query that is issues is taking a decision expecting the END TIME to be null:
or also quoted here:
We can fix that by either:
What do you think? I can submit a PR for either case.
Affects: 3.0.9, 4.0.1, 4.1.0.RC1
Referenced from: pull request #643
Mahmoud Ben Hassine commented
Good catch! Thank you for reporting this. For the fix, I would go for option 2 because option 1 will return the failed job execution as a running execution which is obviously not the case. So setting the end time along with the status to