2 - Routing Layer on Apache Dubbo

2-1 - Routing selection execution failed

Mon, 01 Jan 0001 00:00:00 +0000

Routing selection execution failed

2-2 - No Available Provider (Address Not Found)

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The Provider service is not started, or the registration center (such as ZooKeeper, Nacos, Consul) is down.
There is an error in the Dubbo service configuration; the service name, group (default is Dubbo), and version must all be correct.
The accessed environment is incorrect: typically, we have multiple environments such as development, testing, and production. Sometimes the published service is in the testing environment, but the access call is made from the development environment.

Troubleshooting and Resolution Steps

Access the Ops system of the registration center to check if there is a provider list for the corresponding service; simultaneously check the logs of the server where the caller application is located (generally, each registration service’s client will have corresponding log records) to see if there are records of address information being pushed/pulled.
If not, it indicates that the publisher failed to release the service; check whether the publisher’s application started successfully.
If there is a service, check the registration center connected by the caller application to confirm it matches the expected environment.
If none of the above are problematic, check if routing filter rules have been configured, etc.

This error code’s FAQ page references Kongming’s “Common Dubbo Errors and Solutions”.

2-3 - Route shutdown failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Reasons

User-defined routes are not written according to specifications.

Troubleshooting and Resolution Steps

Refer to the community SPI extension user manual to check the user-defined routes 《SPI Extension User Manual》 .

2-4 - Merger interface loading failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Dubbo provides the SPI extension Merger interface, which aggregates responses from all downstream providers. Dubbo fails to load the configuration when loading user-defined extension Merger interfaces.

Troubleshooting and Resolution Steps

Refer to the community SPI extension usage manual to check the implementation of the user-defined extension Merger interface “SPI Extension Usage Manual” .

2-5 - Filtering Provider Failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Dubbo selects a provider from the list of providers to make a call during load balancing. If the provider list changes during the selection process, read/write conflicts may occur, leading to filtering exceptions.
When the Dubbo retry mechanism encounters a failure in calling the provider, it will re-filter another provider for the call, and exceptions may occur during the re-filtering process.

Troubleshooting and Resolution Steps

Check the list of providers in the registry and the availability of the corresponding providers.
Raise an issue in the community, providing on-site environment information and reproduction steps.

2-6 - The list of providers filtered by conditional routing is empty

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The filtering conditions for the conditional routing provider are empty.
The list of providers filtered by conditional routing is still empty under forced degradation.

Troubleshooting and Resolution Steps

Refer to the community request routing example to adjust the conditional routing configuration.

2-7 - Condition Routing Execution Exception

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The condition routing rules are not configured according to the specifications, resulting in execution exceptions when executing the condition routing filter.

Troubleshooting and Resolution Steps

Refer to community requested routing examples.

2-8 - Provider Returns Exception Response

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The provider itself throws an exception while handling the result.

Troubleshooting and Resolution Steps

Check whether the provider program is functioning normally.

2-9 - Timeout check task failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The Dubbo framework adds a timeout check task to the request invocation, which results in the failure of adding the timeout check task.

Troubleshooting and Resolution Steps

This exception is an internal exception of the Dubbo framework. Please submit an issue in the community, providing environmental information and reproduction steps.

2-10 - Failure to call the service provider

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Dubbo failed to call the service provider and started retrying.
Dubbo continuously failed to retry calling the service provider.
Dubbo reached the retry limit when calling the service provider.

Troubleshooting and Resolution Steps

Check the network connection latency and other network resources between the consumer and the provider.
Use telnet or other tools to check if the corresponding port of the provider can respond normally.
Check if the provider program is running normally.

2-11 - Invalid Tag Routing Rule

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The tag routing rules configured by the user are invalid.
The tag routing addresses configured by the user are invalid.

Troubleshooting and Resolution Steps

Refer to the community tag routing configuration specifications to check the tag routing configuration.

2-12 - The provider application name is empty when using tag routing

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The provider application name is empty when tag routing retrieves from the pushed provider address list.

Troubleshooting and Resolution Steps

This exception is a Dubbo framework internal exception. Please raise an issue in the community, providing environmental information and reproduction steps.

2-13 - Failed to receive loading mesh routing rules

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The routing rule configuration of the mesh is invalid, causing loading exceptions.

Troubleshooting and Resolution Steps

Check the mesh routing rule configuration. Mesh Example。

2-14 - Script routing execution failed

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The script routing rules are invalid, leading to rule parsing failure.
The Dubbo framework failed to execute the script.

Troubleshooting and Resolution Steps

Check whether the script is written according to the specifications.

2-15 - Route rule parsing failed

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The routing rules configured by the user are invalid.

Troubleshooting and Resolution Steps

Examine the configured routing rules.

2-16 - Request retry failed multiple times

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Provider exceptions lead to the consumer failing to retry multiple times.

Troubleshooting and Resolution Steps

Check the health status of the provider.

2-17 - mock request failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Forced mock is configured, indicating log.
Exception occurs during mock request execution.

Troubleshooting and Resolution Steps

Check whether forced mock is configured.
Check if the mock response is normal.

2-18 - Mesh routing rules not being listened to

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

The mesh has issued routing rules, but the rules are not being listened to.

Troubleshooting and Resolution Steps

Check if the mesh routing rule configuration complies with the specifications.

2-19 - Asynchronous Request Failure

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Provider exceptions lead to asynchronous request failures for the consumer.
Network exceptions lead to asynchronous request failures for the consumer.

Troubleshooting and Resolution Steps

Check the health status of the provider.
Check the network status.

2-20 - Failed to Merge Group Result

Mon, 01 Jan 0001 00:00:00 +0000

Possible Causes

Failed to merge group results.

Troubleshooting and Resolution Steps

When returning results, there may be runtime exceptions in the business logic, which can be traced back to the specified line number reported in the console.