-
Notifications
You must be signed in to change notification settings - Fork 525
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
DataIntegrityViolationException instead of DuplicateKeyException #1272
Comments
Thanks for feedback, I have noticed that too. I am working on version 5.x.x which is built on top of Spring 6 and I have already fixed it there. I will check if it makes sense to backport it to version 4.x.x |
Thx, when 5.x.x is released we will upgrade to it |
Hi, version 5.0.0 just released, please let me know if it helped |
If you are using Oracle, it might be caused by this spring-projects/spring-framework#29673 |
It's actually this spring-projects/spring-framework#29511 |
I will fix it in 5.0.1 |
Fixed in Spring 6.0.3 https://github.com/spring-projects/spring-framework/releases/tag/v6.0.3 |
Still broken for MsSQL |
Hi,
We are in the process of upgrading to Spring Boot 3 and see stacktraces in our logs that are caused by shedlock.
It seems that Spring throws a DataIntegrityViolationException and not a DuplicateKeyException anymore.
In our own code we made a workaround to also catch DataIntegrityViolationException and check if the message contains "Duplicate entry".
When the message of the exception contains "Duplicate entry", the exception should be logged on DEBUG level and not ERROR.
This is the stacktrace:
The text was updated successfully, but these errors were encountered: