Skip to content
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

CyclicPropertyReferenceException logged with stack trace [DATAMONGO-1205] #2122

Closed
spring-projects-issues opened this issue Apr 15, 2015 · 1 comment

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Apr 15, 2015

Vinicius Seixas opened DATAMONGO-1205 and commented

I have a document model with a many potential cycles, but it is the way it has to be and the application ensures there will be no cycling documents.

The problem is that the cycle checking is polluting the logs, I get 52 cycle warnings but it generates 3293 lines at the log.

At MongoPersistentEntityIndexResolver.java there are 4 lines with LOGGER.warn codes, 3 of them are "LOGGER.warn(e.getMessage());" and 1 is "LOGGER.warn(e.getMessage(), e);", this last one should be changed to match the others and stop polluting the logs, the stacktrace has no use for this kind of warning.


Affects: 1.6.2 (Evans SR2)

Backported to: 1.10.4 (Ingalls SR4), 1.9.11 (Hopper SR11)

1 votes, 3 watchers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants