-
Notifications
You must be signed in to change notification settings - Fork 617
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
RetryExceptionPredicate has the wrong error messages #2944
Comments
…ages consistent
Excellent catch! Gonna run your build quickly, then merge it. The background here: A while back, it was agreed Spring wide that trailing dots in exception messages should be removed. |
I'm guessing this could/should be backported to 7.3.x, maybe 7.2.x depending on when the change was made? |
I will take care of this for all supported branches. :) |
This fix #2944 by making the retryable exception messages consistent by introducing constants for prematurely closed transactions and sessions omitting the trailing dot as agreed within the bigger Spring Data team.
This fix #2944 by making the retryable exception messages consistent by introducing constants for prematurely closed transactions and sessions omitting the trailing dot as agreed within the bigger Spring Data team.
Thank you! |
org.springframework.data.neo4j.core.support.RetryExceptionPredicate
contains two exception messages that are retryable;Neither of these messages appear anywhere in the code base. However, very similar messages (without a trailing dot) appear in exceptions raised in
org.springframework.data.neo4j.core.transaction.Neo4jTransactionHolder
. Given these exceptions should be retryable, these exception messages should match.(Background; we've been wondering why some exceptions weren't being retried in our code base - finally narrowed it down to this!)
The text was updated successfully, but these errors were encountered: