404988672 opened a new issue #9513:
URL: https://github.com/apache/dubbo/issues/9513


   <!-- If you need to report a security issue please visit 
https://github.com/apache/dubbo/security/policy -->
   
   - [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) 
of this repository and believe that this is not a duplicate.
   
   ### Environment
   
   * Dubbo version: 2.7.8
   * Operating System version: linux
   * Java version: 1.8
   
   ### Steps to reproduce this issue
   
   消费端配置信息
   dubbo:
     cloud:
       subscribed-services:
     registry:
       address: nacos://127.0.0.1:8848
       group: prod
     scan:
       base-packages: ***
     registry:
       check: false
     provider:
       loadbalance: roundrobin
       version: release
     protocol:
       name: dubbo
       port: -1
       serialization: kryo
   
   生产者有两个实例,配置分别为
   1、
   dubbo:
     cloud:
       subscribed-services:
     registry:
       address: nacos://127.0.0.1:8848
       group: prod
     provider:
       loadbalance: roundrobin
       version: 
     protocol:
       name: dubbo
       port: -1
       serialization: kryo
   
   2、
   dubbo:
     cloud:
       subscribed-services:
     registry:
       address: nacos://127.0.0.1:8848
       group: prod
     provider:
       loadbalance: roundrobin
       version: release
     protocol:
       name: dubbo
       port: -1
       serialization: kryo
   
   当消费者连续的发请求,一个成功,一个会失败,失败信息为:
   
![image](https://user-images.githubusercontent.com/38349390/147739427-76b03032-2605-480d-960f-02126ccc3f5f.png)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to