Hi, tien I just curious on why you use `ReferenceConfigCache` to get the reference? Why not using `@Reference` everywhere instead?
best regards, Jason > On Oct 23, 2019, at 16:55, Tien Dat PHAN <[email protected]> wrote: > > Dear > > Related to the topic of this thread, I have a question: > When starting the consumer, we create a reference holder that is initialized > to hold the API reference. We use the ReferenceConfigCache to keep the > reference cache. > We only invoke the ReferenceConfigCache.get(ReferenceConfig<OurAPI>) at the > very beginning of the holder. > This seems to result in bad outcome if the > ReferenceConfigCache.get(ReferenceConfig<OurAPI>) is invoked when the service > provider is not ready (not yet exported). > > Our questions are: > 1. If this is a bad practice, should we invoke the > ReferenceConfigCache.get(ReferenceConfig<OurAPI>) every time we want to use > it? > 2. If the answer to the 1. question is YES. Then our concern is: Does > creating new API reference everytime we use it lead to sub-performance? And > how the system can GC the connection created everytime we invoke > ReferenceConfigCache.get(ReferenceConfig<OurAPI>)? Or we, at the consumer > side, have to handle the connection closeness? > > Best regards > Tien Dat > > On 2019/10/14 09:21:14, 郑泽超 <[email protected]> wrote: >> >> Hello, >> You can set check=false in your reference config >> >>> 在 2019年10月14日，下午4:32，一陣風& <[email protected]> 写道： >>> >>> Start the client first and then start the server to report an error: >>> >>> >>> >>> Failed to invoke the method getBalance in the service >>> com.github.autfish.dubbo.service.BalanceService. No provider available for >>> the service com.github.autfish.dubbo.service.BalanceService from registry >>> localhost:9090 on the consumer 192.168.8.249 using the dubbo version 2.7.1. >>> Please check if the providers have been started and registered. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> How should I configure in yml file >> >>
