Hello,

I have a [3.3.1] Spring boot project and i use Spring Batch(I am letting Spring boot handling the versions of my dependencies except the ones it can't handle like MapStruct for example).

I want to upgrade my project to 3.3.5 and i had an issue where i had this error out of nowhere [org.springframework.orm.jpa.JpaSystemException: A problem occurred in the SQL executor : JDBC parameter value not bound - null] and [Caused by: org.hibernate.sql.exec.ExecutionException: A problem occurred in the SQL executor : JDBC parameter value not bound - null]

This happens when my repository methodName is executed by the RepositoryItemReader. Before, continuing i will provide you with an image that shows that i provide all of the parameters for the method and that i can only see them at the version [3.3.1] but not in all the upper versions[3.3.2] and beyond.

This is an example of the definition of the method in question :

Capture d’écran 2024-10-30 à 17 50 03

This image is for Spring boot [3.3.1] and down :

Capture d’écran 2024-10-30 à 17 17 09

This image is for spring boot [3.3.2] and up :

Capture d’écran 2024-10-30 à 17 25 17

I do suspect the pagination and i mean by that the first argument in the request Capture d’écran 2024-10-30 à 17 34 25

Here are more images of the exception because i tried to debug to understand a little bit what's happening : Capture d’écran 2024-10-30 à 14 58 53

Capture d’écran 2024-10-30 à 17 00 03

Comment From: wilkinsona

Spring Boot isn't really involved in Spring Batch's use of JPA and is unlikely to be the cause of your problem. More likely is that the cause is a bug in Spring Batch or Hibernate. If you'd like some further assistance, please create a minimal sample that works with Spring Boot 3.3.1 and fails when upgraded to 3.3.2 and then open a Spring Batch issue so that the Batch team can investigate.