Closed lin1005q closed 2 years ago
@OlgaMaciaszek
Hello @lin1005q, please provide a minimal, complete, verifiable example that reproduces the issue.
@OlgaMaciaszek
Hello @lin1005q - thanks for providing a sample. Will take a look tomorrow.
Hello @lin1005q. This happens, because you've added the LB configuration bean to a class where your root application context is configured. As you can read in the docs, classes containing LB configuration beans should be passed as configuration
argument of the @LoadBalancerClient
annotation and they should not be annotated with @Configuration
(or any meta-annotations that include it, such as @SpringBootApplication
). This way, the beans will be created in specific child contexts, a different one for every load-balanced service. This change fixes the setup.
Thank you very much. How can it be set as the global default, which is automatically configured like xxx-spring-boot-starter. No need to manually add the @LoadBalancerClient annotation
If you want to set a custom configuration, you need to use the annotation. If you want to have a default for many clients, you can use @LoadBalancerClients(defaultConfiguration= CustomConfig.class)
. Please read the docs - it's all described there.
Describe the bug Please provide details of the problem, including the version of Spring Cloud that you are using.
add this code
throw cache about NPE
.withCaching()
throw 503 error.hint
bean config success.Sample If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it.