Search:

what does not working here mean? all the jobs hang there? what is the configuration of your taskExecutor?

using tasklet is enough from my point of view(you need re-excute if trancate table or whole job failed), what is the detail error information you got when use tasklet? , i guess that error might...

why not using jobExecution.stop()?

Is it possible to pass the jobId of the scheduler to spring batch when the job is launched
------------
why not put the jobId of the scheduler into the job parameters of the JobExecution of spring...

implement your own itemWriter or use the ItemTransformerItemWriter / the CompositeItemWriter

hope you will never see the issue any more :)

the MySQLMaxValueIncrementer works in the way as the following, i can't image how multi-rows will be generated. and i don't think we need care about transaction supportable or not here.
...

that really confused me,
i assume you are using the org.springframework.jdbc.support.incrementer.MySQLMaxValueIncrementer to interact with these MySQL SEQ tables;
which will not bring multi rows...

here is an option for you recommandation

store the file name as job parameter
cache the jobExecution(include job parameter) instance before job start(using JobListener),make this cache singleton...

did the 2 jobs lunch by diffrent processes has the same execution_id? would you post the dumpped JobExecution information when above error occures? thanks

B.1.1. Version
Many of the database tables discussed in this appendix contain a version column. This column is important
because Spring Batch employs an optimistic locking strategy when dealing...

jobexecution.getJobInstance().getJobName()