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
WARN 764 --- [ main] SpelExpressionStringQueryParameterBinder : Setting the parameter with name '__$synthetic$__4' and position 'null' lead to an exception. #293
Comments
To reproduce please unpack the attached *.zip file, import the project into an STS workspace and run the JUnit test PlayerStatisticsRepositoryTest. |
Thanks for this. We added the logging recently, to hunt down when exactly a certain exception handler was triggered. So it looks like we found at least one case. I'll look into it. |
In any case, you can probably ignore the exception, e.g. by excluding the logger 'org.springframework.data.jpa.repository.query.SpelExpressionStringQueryParameterBinder' If you ever see other exceptions related to parameter binding gone wrong (like the claim that a required parameter wasn't bound, the information from this logger might actually contain more helpful information. The logging was introduced as part of https://jira.spring.io/browse/DATAJPA-1172 |
This issue will be tracked under https://jira.spring.io/browse/DATAJPA-1179 since it is not related to the examples. |
Thanks for all the hints. Switching off the logging for |
@PawelJagus I have the same issue with spring boot 1.5.9 could you help me how it work with you by example |
@mostafaarefaat I added the following line to my
|
I have just switched from Spring Boot 1.5.3 to 1.5.7 and suddenly the following warning started to show up on executing one of my JPA Repository unit test.
This does not happen when I fall back to 1.5.3. It looks like this is printed with Throwable.printStackTrace() because the tests are running all green.
The text was updated successfully, but these errors were encountered: