-
Notifications
You must be signed in to change notification settings - Fork 617
Intermitent error mapping Record #2585
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
Comments
Hi and thanks for reporting this. Usually there is a root cause behind the |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Hi @meistermeier, sorry for the response delay. Based on mapping:
And based on JPA repository:
Here is the complete stack I have:
|
Thanks for the feedback. One more question: Does the error happen spontaneously during the lifetime of the application or between multiple runs?
is empty in https://github.com/spring-projects/spring-data-neo4j/blob/6.2.5/src/main/java/org/springframework/data/neo4j/core/mapping/NodeDescriptionStore.java#L56 |
Hi @meistermeier, sorry I am not receiving alerts on my e-mail about your responses :/ Yep, the error happens spontaneously during the lifetime of the application. From my pom.xml here are the properties:
|
It worth noting that the problem is not related to the specific Node-Relationship, it is general and happens with any query :/ . Also by analysing the code at https://github.com/spring-projects/spring-data-neo4j/blob/6.2.5/src/main/java/org/springframework/data/neo4j/core/mapping/NodeDescriptionStore.java#L57 I would guess it is probably related to a race condition Here are the latest errors:
|
Hi @meistermeier any return on this |
Sorry, that I did not response. Unfortunately I couldn't reproduce the problem. Since I have no idea how to get this failing on my machine, I created a branch that you can check out against your test suite. There will be a |
Hi @meistermeier, tks for the snapshot ... as soon as it is available I will test against it |
Hi @meistermeier I got to reproduce the error using this block of code:
Sometimes it throws the error I had pasted before :)
Now I will try using the SNAPSHOT of yours |
Hi @meistermeier is there any specific repository path for the 6.3.4-GH-2585-SNAPSHOT? I had updated my pom and received:
|
This would be:
Typically the snapshot repo is sufficient, but for completeness I added also the milestone repo. Thanks for the reproducer. I will have a look right now. |
Unfortunately, I cannot reproduce it with the snippet above :( |
Hi @meistermeier, sure. Do you mean anonymised data or the missing classes? By the way over my tests, 1 out of 30 executions throw the error :/ |
Hi @meistermeier, I just tested with the SNAPSHOT version but now I am getting a different error:
Should I update any other library version such as JPA? Currently I am using the spring-data-jpa version 2.6.2 |
Looks like the Spring Data commons dependency from the snapshot (2.7.4-SNAPSHOT) does not get picked up and your project sticks with 2.7.2 defined as a transitive dependency of JPA. Did you maybe define this explicitly somewhere in your project definition (pom.xml / build.gradle)? |
Hi @meistermeier, sorry for the long delay on my response... I was traveling and I was away from the computer ;) So, I got to test with the following versions and the error was not thrown anymore ;)
So I guess the changes you have made took a positive effect ;) When those changes could be onboarded on the latest release? |
Sorry I missed this yesterday. If everything works out as expected, the release should go out today. |
Hi @meistermeier is the changes on the release https://github.com/spring-projects/spring-data-neo4j/releases/tag/6.3.5 ? |
Yes, this is the release. There was a problem in the release pipeline that's why 6.3.5 is now current and 6.3.4 was more or less skipped. |
Tks much :) |
Hi guys, I am using the current configuration:
And frequently I am facing an error which a record could not be mapped. The problem is that this error is intermitent, the same Node sometimes work and others do not. My best guess is some race condition or anything related to that.
Here is the stack using a simple JPA findByCode():
The text was updated successfully, but these errors were encountered: