[D] Invocation Failure When Testing Application-Level Registration in Dubbo 3.x Based on the Sample Configuration [dubbo]

Thu, 22 Jan 2026 01:14:13 -0800 


GitHub user qq31715879 created a discussion: Invocation Failure When Testing 
Application-Level Registration in Dubbo 3.x Based on the Sample Configuration

### Pre-check

- [X] I am sure that all the content I provide is in English.


### Apache Dubbo Component

Java Samples (apache/dubbo-samples)

### Details

Below is a clear and GitHub-friendly English translation. I have kept the 
configuration blocks and error messages intact, and translated only the 
descriptive text.

---

### Provider configuration

```yaml
dubbo:
  application:
    name: nest-test
    qos-enable: true
    qos-port: 22222
    qos-accept-foreign-ip: false
    logger: slf4j
  protocol:
    name: tri
#    name: dubbo
    port: 50051
  registry:
    address: nacos://${nacos.address:127.0.0.1}:8848
    register-mode: instance
```

### Consumer configuration

```yaml
dubbo:
  application:
    name: dubbo-springboot-demo-consumer
    logger: slf4j
#  protocol:
#    name: dubbo
#    port: 20880
  registry:
    address: nacos://${nacos.address:127.0.0.1}:8848
    register-mode: instance
```

### Error

```
Failed to check the status of the service 
com.digiwin.nest.test.client.api.TestDubboApi.
No provider available for the service 
com.digiwin.nest.test.client.api.TestDubboApi
from the url 
consumer://192.168.202.151/com.digiwin.nest.test.client.api.TestDubboApi
?application=dubbo-springboot-demo-consumer
&background=false
&dubbo=2.0.2
&executor-management-mode=isolation
&file-cache=true
&interface=com.digiwin.nest.test.client.api.TestDubboApi
&logger=slf4j
&methods=queryOrder
&pid=25336
&register.ip=192.168.202.151
&release=3.3.3
&side=consumer
&sticky=false
&timestamp=1769072507846
&unloadClusterRelated=false

to the consumer 192.168.202.151 using Dubbo version 3.3.3
```

---

### Still fails even when keeping the service (application) name consistent 
with the provider

```yaml
dubbo:
  application:
    name: nest-test
    logger: slf4j
#  protocol:
#    name: dubbo
#    port: 20880
  registry:
    address: nacos://${nacos.address:127.0.0.1}:8848
    register-mode: instance
```

### Error

```
Failed to check the status of the service 
com.digiwin.nest.test.client.api.TestDubboApi.
No provider available for the service 
com.digiwin.nest.test.client.api.TestDubboApi
from the url 
consumer://192.168.202.151/com.digiwin.nest.test.client.api.TestDubboApi
?application=nest-test
&background=false
&dubbo=2.0.2
&executor-management-mode=isolation
&file-cache=true
&interface=com.digiwin.nest.test.client.api.TestDubboApi
&logger=slf4j
&methods=queryOrder
&pid=37628
&register.ip=192.168.202.151
&release=3.3.3
&side=consumer
&sticky=false
&timestamp=1769073022340
&unloadClusterRelated=false

to the consumer 192.168.202.151 using Dubbo version 3.3.3
```

---

If you want, I can further polish this into a **standard Dubbo GitHub issue 
template** (Background / Expected Behavior / Actual Behavior / Environment / 
Reproduction Steps).


### Code of Conduct

- [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


GitHub link: https://github.com/apache/dubbo/discussions/16037

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to