Closed amizurov closed 1 year ago
The trigger for the Spring Native related configuration is EurekaClientAutoConfiguration
, maybe it is not enable in your application. Could you check if it is active by watching the report generated with --debug
when running the app on the JVM?
@sdeleuze Thanks for you reply. Just to clarify this is not a problem in my custom project it's also problem in sample. If you just up the eureka server
without any application instance registered and run the native discoveryclient
everything will work. But if you register any application instance (e.g. configserver or another app) and re-run discoveryclient
it will fail with the issue which i'm described above. When a I add the following hints to the sample, it starts working
@TypeHint(types = { Application.class, InstanceInfo.class, MyDataCenterInfo.class }, typeNames = {
"com.netflix.appinfo.InstanceInfo$PortWrapper",
})
@OlgaMaciaszek Please make sure we support this use case with Spring Boot 3.
Yes, I'm planning to start testing Eureka client integration today (we've only recently published the first Eureka Client 4.x
milestone).
It works fine on Spring Cloud 2022.x
now. A PR with sample has been submitted. We're not planning to further work on Spring Native project.
Hello folks, i'm trying to build a spring-boot native application with
spring-cloud-starter-netflix-eureka-client
integration but i got the exception on startup:Reproducer: Build the sample application discoveryclient and run it.
After I manually added hints:
everything worked. But if i understand correct all required hints already present in spring-native-configuration
Could you tell me if this is a bug or am I doing something wrong ?