zrlw
zrlw
could you try 3.3.5 or the lastest codes?
if you just saw "Failed to connect to server" in your log file, it might be ok because ```ReconnectTimerTask``` will retry connect to the servers which connection are broken until...
i checked the pr codes, they are logical equivalent of origin codes. but i suggest it might be better to refactor it as a method-by-method separation.
spotless:apply
```dubbo-spring6-security``` should be added to the pom.xml if the project uses ```OAuth2AccessToken``` since it's only be supported with ```spring6``` / ```spring-boot 3```.
could you debug or add log info at ReferenceBeanManager#setApplicationContext to check the moduleModel value? ``` @Override public void setApplicationContext(ApplicationContext applicationContext) throws BeansException { this.applicationContext = applicationContext; moduleModel = DubboBeanUtils.getModuleModel(applicationContext);
> I hope you can find the root cause and best way. it might be too early to get ```moduleModel``` at ```ReferenceBeanManager#setApplicationContext``` because it might not be created yet.
> > prepareReferenceBeans > > OK,this solution by moving to prepareReferenceBeans will be tried later. any progress? @imgoby
see https://github.com/apache/dubbo-integration-cases/blob/main/99-integration/dubbo-samples-memory-tri-server/src/test/java/org/apache/dubbo/samples/client/GreetingServiceIT.java destroy current FrameworkModel doesn't mean all ApplicationModels could be destroyed.