zrlw commented on issue #15305:
URL: https://github.com/apache/dubbo/issues/15305#issuecomment-2989529649
i tested under nacos 2.5.1 enviroment (both client and server use 2.5.1)
and got same successful result.
1. modified provider and consumer pom to support nacos 2.5.1
```
<dependency>
<groupId>org.apache.dubbo</groupId>
<artifactId>dubbo-spring-boot-starter</artifactId>
<version>3.3.6-SNAPSHOT</version> <!-- mvn install on dubbo
current 3.3 branch: 2025/06/20 -->
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-log4j2</artifactId>
<version>3.2.3</version>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter</artifactId>
<version>3.2.3</version>
<exclusions>
<exclusion>
<artifactId>spring-boot-starter-logging</artifactId>
<groupId>org.springframework.boot</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.alibaba.nacos</groupId>
<artifactId>nacos-client</artifactId>
<version>2.5.1</version>
</dependency>
<!-- incompatible -->
<!-- <dependency>-->
<!-- <groupId>org.slf4j</groupId>-->
<!-- <artifactId>slf4j-api</artifactId>-->
<!-- <version>1.7.36</version>-->
<!-- </dependency>-->
```
2. add annotations: ```@EnableDubbo``` ```@DubboService```
```@SpringBootApplication``` to provider.
3. test
```
step 1: delete .dubbo at home directory
step 2: start nacos 2.5.1 server
step 3: clean all mapping files under
${home}/nacos/config/Config-fixed-X.X.X.X_8848_nacos/snapshot
step 4: start provider on 20880, java -jar -DappName=demo-provider
-Dport=20880 target/provider.jar
step 5: start consumer, java -jar target/consumer.jar
step 6: start provider on 20881, java -jar -DappName=demo-provider2
-Dport=20881 target/provider.jar
```
4. get consumer output
As for me, you might focus Nacos bugfix notification from Nacos:
https://github.com/alibaba/nacos/releases
--
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]
