You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***************************
APPLICATION FAILED TO START
***************************
Description:
The bean 'dataSourceNameResolver', defined in class path resource [net/ttddyy/observation/boot/autoconfigure/DataSourceObservationAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [com/github/gavlyukovskiy/boot/jdbc/decorator/DataSourceDecor
atorAutoConfiguration.class] and overriding is disabled.
Not sure who has to fix their bean naming, but it would be nice if any one of you would fix it :)
The text was updated successfully, but these errors were encountered:
It looks like both libraries have defined a bean with the same name - dataSourceNameResolver. com.github.gavlyukovskiy.boot.jdbc.decorator.DataSourceNameResolver and net.ttddyy.observation.boot.autoconfigure.DataSourceNameResolver.
Since both bean definitions have @ConditionalOnMissingBean, I think a quick workaround is that if you define either bean with a different name in your application configuration, the one from auto-configuration should back off.
When using JDBC observability linked from official Spring Boot documentation https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html#actuator.observability -> https://jdbc-observations.github.io/datasource-micrometer/docs/current/docs/html/ and including the mentioned spring boot starter
Application startup fails when datasource-proxy-spring-boot-starter project is also present as a dependency
Error:
Not sure who has to fix their bean naming, but it would be nice if any one of you would fix it :)
The text was updated successfully, but these errors were encountered: