jk-tonycui opened a new issue, #16130:
URL: https://github.com/apache/dubbo/issues/16130

   ### Pre-check
   
   - [x] I am sure that all the content I provide is in English.
   
   
   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache Dubbo Component
   
   Java SDK (apache/dubbo)
   
   ### Dubbo Version
   
   Dubbo 3.3.6, JDK 1.8
   
   ### Steps to reproduce this issue
   
   When configuring condition route to route traffic to particular instance, 
there is still traffic in others
   
   ### What you expected to happen
   
   The route config should be executed exactly. When configuration is set, 
traffic should follow the configuration to route traffic to the specified 
instance.
   
   ### Anything else
   
   After debugging, the root cause is the code below in `AbstractStateRouter`
   ```
   routeResult = doRoute(invokers, url, invocation, needToPrintMessage, 
nodeHolder, messageHolder);
           if (routeResult != invokers) {
               routeResult = invokers.and(routeResult);
           }
   ```
   
   `invokers.and` should only return the invokes that contains in both lists, 
but the implementation of and function is adding the tailList together. 
Therefore ,the final routeResults are redundant.  
   
   ### Do you have a (mini) reproduction demo?
   
   - [ ] Yes, I have a minimal reproduction demo to help resolve this issue 
more effectively!
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [x] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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