wangdechong commented on issue #15641:
URL: https://github.com/apache/dubbo/issues/15641#issuecomment-3200407571
> set dubbo.onlyUseMetadataV2 of your provider to false
The configuration dubbo.application.only-use-metadata-v2=false has been set,
but no obvious changes have been observed.
```
spring:
application:
name: uupt-middle-ackdemo-service
dubbo:
registry:
address:
nacos://${nacos.address:127.0.0.1}:8848?username=nacos&password=nacos
register-mode: instance
application:
name: ${spring.application.name}
qos-enable: true
only-use-metadata-v2: false
protocols:
tri:
name: tri
port: 8080
dubbo:
name: dubbo
port: 20880
``
After upgrading the consumer from 3.1.11 to 3.3.5, it directly calls the
org.apache.dubbo.metadata.MetadataServiceV2 interface to obtain metadata, which
can be matched normally, so there is no such issue. How to smoothly migrate
from 3.1.11 to 3.3.5? The exception example is demonstrated in the attached
source code. please help check how to handle this issue further?
[springboot2-dubbot3.3.zip](https://github.com/user-attachments/files/21854675/springboot2-dubbot3.3.zip)
--
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]
