Step with JdbcCursorItemReader doesn't run at the second round in Spring Batch 6

[owox27]

Hi all,
After migration to Spring Batch 6.0, my reader doesn't work correctly.
Everything is fine at the first running, but skip the step at the second round,
and all would be fine again at the first running after the project restart.

Works fine version: spring-boot-starter-parent 3.5.8 + spring-boot-starter-batch
Goes wrong version: spring-boot-starter-parent 4.0.0 + spring-boot-starter-batch-jdbc

Job config

    public Job testJob(Step testStep) {
        return new JobBuilder("test job", jobRepo)
                .start(testStep)
                .build();
    } 
    @Bean
    public Step testStep(JdbcCursorItemReader<String> reader) {
        return new ChunkOrientedStepBuilder<String, String>("test step", jobRepo, 1000)
                .reader(reader)
                .writer(new PrintItemWriter<>())
                .build();
    }

    @Bean
    public JdbcCursorItemReader<String> testReader() {
        return new JdbcCursorItemReaderBuilder<String>()
                .name("test reader")
                .sql("select AAA from BBB where CCC='DDD' ")
                .dataSource(dataSrc)
                .rowMapper(new SingleColumnRowMapper<>(String.class))
                .build();
    }

Run config

JobParametersBuilder builder = new JobParametersBuilder().addLong("time", System.currentTimeMillis());

Debug log (first round)

2025-12-15 09:53:50.619 [DEBUG] TransactionManager - Creating new transaction with name [null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT
2025-12-15 09:53:50.629 [INFO ]    PrintItemWriter - Read item: 7005
2025-12-15 09:53:50.630 [INFO ]    PrintItemWriter - Read item: 7001
2025-12-15 09:53:50.630 [INFO ]    PrintItemWriter - Read item: 7004
2025-12-15 09:53:50.630 [DEBUG] TransactionManager - Creating new transaction with name [org.springframework.batch.core.repository.support.SimpleJobRepository.updateExecutionContext]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT
2025-12-15 09:53:50.634 [DEBUG] TransactionManager - Acquired Connection [HikariProxyConnection@102612499 wrapping ConnectionID:2 ClientConnectionId: e0c3ce6c-55d2-4753-929d-ddd29eb7f4c8] for JDBC transaction
2025-12-15 09:53:50.634 [DEBUG] TransactionManager - Switching JDBC Connection [HikariProxyConnection@102612499 wrapping ConnectionID:2 ClientConnectionId: e0c3ce6c-55d2-4753-929d-ddd29eb7f4c8] to manual commit
2025-12-15 09:53:50.638 [DEBUG]       JdbcTemplate - Executing prepared SQL update
2025-12-15 09:53:50.638 [DEBUG]       JdbcTemplate - Executing prepared SQL statement [UPDATE TB_STEP_EXECUTION_CONTEXT
SET SHORT_CONTEXT = ?, SERIALIZED_CONTEXT = ?
WHERE STEP_EXECUTION_ID = ?
]
2025-12-15 09:53:50.642 [DEBUG] TransactionManager - Initiating transaction commit
2025-12-15 09:53:50.642 [DEBUG] TransactionManager - Committing JDBC transaction on Connection [HikariProxyConnection@102612499 wrapping ConnectionID:2 ClientConnectionId: e0c3ce6c-55d2-4753-929d-ddd29eb7f4c8]
2025-12-15 09:53:50.670 [DEBUG] TransactionManager - Releasing JDBC Connection [HikariProxyConnection@102612499 wrapping ConnectionID:2 ClientConnectionId: e0c3ce6c-55d2-4753-929d-ddd29eb7f4c8] after transaction
2025-12-15 09:53:50.671 [DEBUG] TransactionManager - Resuming suspended transaction after completion of inner transaction
2025-12-15 09:53:50.671 [DEBUG] TransactionManager - Initiating transaction commit
2025-12-15 09:53:50.671 [DEBUG] TransactionManager - Committing resourceless transaction on [org.springframework.batch.infrastructure.support.transaction.ResourcelessTransactionManager$ResourcelessTransaction@1d743a78]
2025-12-15 09:53:50.672 [DEBUG]       AbstractStep - Step execution success: id=194
2025-12-15 09:53:50.672 [INFO ]       AbstractStep - Step: [test step] executed in 93ms

Debug log (second round)

2025-12-15 09:53:56.240 [DEBUG]       AbstractStep - Step execution success: id=195
2025-12-15 09:53:56.240 [INFO ]       AbstractStep - Step: [test step] executed in 33ms

Thank you for your help !

[owox27]

UPDATE

Fixed in the new version.
Problem disappeared after upgrade to spring-boot-starter-parent 4.0.1.

[fmbenhassine]

Thank you for confirming the fix in Spring Batch 6.0.1 / Spring Boot 4.0.1