You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The modification of the version of seata-discovery-core module to 1.5.2 by the dubbo-filter-seata module resulted in the example service and seata-server being able to obtain corresponding instances in different nacos groups (SEATA_GROUP).
Which Component
Spring Cloud Alibaba:
2022.0.0.0-RC1
, Seata:1.7.0-SNAPSHOT
, Nacos Client:2.2.1-RC
, Nacos Server:1.4.x
or2.x
Describe the bug
master (1.6.1)
branch and the functionality is work.develop (1.7.0-SNAPSHOT)
branch code, an exception will be thrown: "No available service"To Reproduce
develop
branch code:mvn clean install -Dmaven.test.skip=true
pom.xml
file in thespring-cloud-alibaba-dependencies
module (only for testing purposes):readme-zh.md
in the examples section.See examples: https://github.com/alibaba/spring-cloud-alibaba/tree/2022.x/spring-cloud-alibaba-examples/seata-example
http://127.0.0.1:18081/seata/feign
, and you will see the following exception message:AbstractNettyRemotingClient.java
It seems that
RegistryFactory.getInstance().aliveLookup(transactionServiceGroup)
is unable to discover other services.The text was updated successfully, but these errors were encountered: