That behavior is correct. The ItemWriter receives a list of items to write. If a skippable exception is thrown, Spring Batch attempts to determine which item actually caused the exception so only that item is skipped. The way this is done is the transaction is rolled back, the commit interval is changed to 1, and … Read more
I agree with Michael Minella: Spring batch job repository does not like to share its transaction manager with others. The logic is simple, if you share your job transaction manager with your step transaction manager upon step failure it will rollback both the step and the data written to the job repository. This means that … Read more
Create a Split and you will be able to use multithreading between the different branches. Use a TaskExecutor to define your parallelism policy. See Multi-threaded Step Be sure to use the latest version of Spring Batch if you want to use multithreading and the MapJobRepository (prior to latest version, this JobRepository was not thread safe).
The main problem here is that FlatFileItemReader assumes you have line breaks, which you don’t. The clearest solution to me is to copy/paste the class and swap out the readLine() method with one that takes in the appropriate number of characters. Unfortunately, because much of the class is private, you can’t easily extend and override. … Read more
With SpringBoot 2.x, the solution is simpler. You have to extend the DefaultBatchConfigurer class like this: @Component public class NoPersistenceBatchConfigurer extends DefaultBatchConfigurer { @Override public void setDataSource(DataSource dataSource) { } } Without datasource, the framework automatically switches to use the MapJobRepository.
you have at least 4 possibilities: use the ExecutionPromotionListener to pass data to future steps use a (spring) bean to hold inter-step data, e.g. a ConcurrentHashMap without further action this data won’t be accessible for a re-start access the JobExecutionContext in your tasklet, should be used with caution, will cause thread problems for parallel steps … Read more
This may be a bug (we’re still investigating), however we do have a work around. The cause of this is that when using @EnableBatchProcessing the StepScope that is automatically configured assumes java config and therefore does not proxy the step scoped beans, causing them to be created too soon. The work around is to manually … Read more
UPDATE: As of spring 2.5.0, you should use spring.batch.jdbc.initialize-schema instead. See source. With Spring Boot 2.0 you probably need this: https://docs.spring.io/spring-boot/docs/2.0.0.M7/reference/htmlsingle/#howto-initialize-a-spring-batch-database spring.batch.initialize-schema=always By default it will only create the tables if you are using an embedded database. Or spring.batch.initialize-schema=never To permanently disable it.
Just add : @SpringBootApplication(exclude = {DataSourceAutoConfiguration.class }) works for me. I was getting same error I tried with @EnableAutoConfiguration(exclude=…) didn’t work. For those that are wondering where to add @SpringBootApplication(exclude = {DataSourceAutoConfiguration.class }), as it has been asked by user as well. You need to add it to the main Application class which is under … Read more
There is a specific interface for this problem called ResourceAware: it’s purpouse is to inject current resource into objects read from a MultiResourceItemReader. Check this thread for further information.