New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BatchStatus#isRunning() is not consistent with JobExplorer#findRunningJobExecutions(String) or JobExecution#isRunning() #1483
Comments
Alexis SOUMAGNE commented Up! |
I also encountered a problem related to this issue. That is, when launching multi jobs with same parameters in multi threads, there should be only one job can succeed, but actually, there would be more than one job can succeed. I find it is caused by SimpleJobRepository#createJobExecution, this method uses
|
- A running status is STARTING, STARTED, or STOPPING. - Make the order when iterating the return value by JdbcJobExecutionDao.findRunningJobExecutions consistent which the result set of the sql. Resolves spring-projects#1483
- A running status is STARTING, STARTED, or STOPPING. Resolves spring-projects#1483
- A running status is STARTING, STARTED, or STOPPING. Resolves spring-projects#1483
- A running status is STARTING, STARTED, or STOPPING. Resolves spring-projects#1483
- A running status is STARTING, STARTED, or STOPPING. - Update related tests. Resolves spring-projects#1483
Alexis SOUMAGNE opened BATCH-2114 and commented
In STOPPING status should be considered as a "running" status.
The endTime is null until job status is STOPPED. Which means that the job did not recieved interuption signal yet.
Simply the code should be :
Affects: 2.2.2
The text was updated successfully, but these errors were encountered: