Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reactive firestore repositories cause bean dependency cycle when used in a MeterBinder
See original GitHub issueSpring Boot version: 2.6.7 Spring cloud gcp version (BOM): 3.2.1
We seem to be running into an issue similar to https://github.com/spring-projects/spring-boot/issues/27591.
We recently migrated one of our metric sources to use a spring data repository. This seems to cause a bean dependency cycle caused by startupTimeMetrics (See attached bean cycle screenshot).
Looks to me like Firestore repositories cause the metrics stack to be initialized, which then causes a cycle if the repository is used in a Meterbinder.
A project to reproduce the issue is located at https://github.com/JakobFels/FirestoreMetricsReproducer
Issue Analytics
- State:
- Created a year ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks, @elefeint. I’ve re-opened the Spring Boot issue.
Right; because spring-data-jpa does not implement
RepositoryFactoryBeanSupport. But spring-data-r2dbc does, so it makes for a good reproducer.https://github.com/elefeint/FirestoreMetricsReproducer/tree/h2-reproducer shows the same issue with H2 R2DBC driver.
While implementing
MeterBinderworks in principle, when combined withRepositoryFactoryBeanSupport, and likely other event-publishing infrastructure, the end-user application ends up creating a cycle.