hehuang139 commented on issue #15641:
URL: https://github.com/apache/dubbo/issues/15641#issuecomment-6268512250

   Reproduced this with a provider built from the current `3.3` branch, named 
`dubbo` and `tri` protocols, local metadata, `only-use-metadata-v2=false`, and 
a released Dubbo 3.1.11 consumer. V1 was exported over Dubbo while the 
advertised metadata URL pointed to the Triple V2 endpoint; the consumer failed 
with `UNIMPLEMENTED: Invoker for gRPC not found`.
   
   Submitted #16525. Both metadata versions now use Triple when V2 is enabled, 
and the advertised URL supports legacy V1 consumers while preserving V2 
negotiation. Explicit metadata protocol settings are also respected.
   
   The same Dubbo 3.1.11 consumer retrieved metadata successfully after the 
fix. Validation on Linux with JDK 17 passed 8 RPC/customizer tests, all 35 
metadata API tests, and `spotless:check` for both changed modules.
   


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