1 - Registry Center Layer on Apache Dubbo

1-1 - Invalid Address

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

This log can be ignored; the service version or group does not match. It only appears in the Zookeeper registry and this check has been removed in version 3.1.7.

Possible Causes

The service.group configured on the Provider side does not match the reference.group configured on the Consumer side (i.e., the service group configuration).
The service.version configured on the Provider side does not match the reference.version configured on the Consumer side (i.e., the service version configuration).

Troubleshooting and Resolution Steps

Can be ignored; this check has been removed in version 3.1.7.

1-3 - URL destruction failure

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

Possible Causes

When the FrameworkExecutorRepository is destroyed, calling CacheableFailbackRegistry.evictURLCache can lead to destruction failure, resulting in an error code.

Troubleshooting and Resolution Steps

Also refer to Configuration Item Reference Manual

1-4 - Empty Address

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

Possible Causes

The 1-4 error in registry.integration.RegistryDirectory is caused by invokerUrls being empty during the refreshInvoker process, which can be ignored.
The 1-4 error in registry.support.CacheableFailbackRegistry may be caused by a mismatch between the consumer and provider, and the “empty protection” being disabled.

Troubleshooting and Resolution Steps

Ensure that the service group configurations on both the Provider and Consumer sides correspond.
Ensure that the service version configurations on both the Provider and Consumer sides correspond.
Check whether enable-empty-protection in the registry center is set to true (default is true).

See also Configuration Reference Manual

1-5 - Received URL with no parameters

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

Possible Causes

When calling CacheableFailbackRegistry.toUrlsWithoutEmpty, if the parameter Collection<String> providers contains a provider that has no parameters, a URL with no parameters will be received.

Troubleshooting and Resolution Steps

This error is an internal error of Dubbo. If you encounter it, you can create an issue on GitHub and provide the error information along with reproduction steps. We will assist you in resolving the issue.

See also Dubbo Community

1-6 - Error clearing URL cache

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

Possible Reasons

Errors occurring while clearing the URL cache in CacheableFailbackRegistry.RemovalTask will trigger an error in clearing the URL cache.

Troubleshooting and Resolution Steps

This error is an internal Dubbo error. If you encounter it, please create an issue on GitHub and provide the error message along with reproduction steps. We will assist you in resolving the issue.

Also refer to Dubbo Community

1-7 - Notification registration event failure

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

Possible Causes

When applied to platforms based on the xDS protocol, it is necessary to notify the consumer when the metadata is updated. If a consumer is offline, it may cause the notification to fail and remove the corresponding consumer’s listener.

Troubleshooting and Resolution Steps

Please also refer to Registry Center - Configuration Item Reference Manual

1-8 - Failure to unregister (unsubscribe) address during destruction

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

Possible Reasons

The error during consumer unregistration or unsubscription may be caused by a failure of the registry center.
The corresponding provider may not have been successfully published.

Troubleshooting and Resolution Steps

Check whether the registry center is operating normally.
Check whether the provider has been successfully published.
Check the relevant parameters of the provider for the registry center, such as registry, config-center, and metadata-report, to ensure they are configured correctly.

See also Configuration Item Reference Manual

1-9 - Failure to read and write the registry service cache

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

Possible Causes

Multiple Dubbo processes (or other Java processes) are using the same cache file.
Failure to read and write due to filesystem permission issues on the directory where the cache file is located.
Incorrect input for the value of dubbo.registry.file.
Accidentally specified two registries to use the same file storage.

Tip: If dubbo.registry.file is not specified, the cache path for the registry service defaults to the ~/.dubbo directory (where ~ is the user’s HOME directory)

1-10 - Failed to read and write the service cache of the registry

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

Possible Causes

Multiple Dubbo processes are using the same cache file.
In the case of multiple registries, multiple registries are specified to use the same file for storage.

Troubleshooting and Resolution Steps

This error often occurs together with error 1-9. Check if multiple Dubbo processes are using the same cache file or if multiple registries are specified to use the same cache file.

See also Configuration Reference Manual for the Registry

1-11 - Service instance registration failure

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

Possible Causes

It might be due to an error in the SPI/IOC configuration of the Registry.

Troubleshooting and Resolution Steps

This error is an internal error of Dubbo. If you encounter it, you can create an Issue on GitHub and provide the error information and reproduction steps, and we will assist you in resolving the issue.

See also Dubbo Community

1-12 - Instances of "Registered Service" have been destroyed

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

Possible Causes

During the graceful shutdown of Dubbo, deregistration is performed by calling destroyAll of AbstractRegistryFactory.

In the process of destroying unexport of Registryprotocol, there may be an attempt to obtain the already destroyed registry through getRegistry of AbstractRegistryFactory, leading to “Instances of Registered Service have been destroyed.”

Troubleshooting and Resolution Steps

See also Configuration Item Reference Manual

1-13 - Failed to execute retry task

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

Possible Causes

The registry center is offline.

Troubleshooting and Resolution Steps

Check if the registry center is functioning properly.
Check if the server where the registry center is located and its network are functioning properly.

1-14 - Dynamic Configuration Recognition Failure

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

Possible Causes

When using the service governance features of Dubbo Admin for dynamic configuration, incorrect content or format of the configuration file may result in the inability to parse the dynamic configuration content, leading to error 1-14.

Troubleshooting and Resolution Steps

Please check whether the content or format of the dynamic configuration file is correct.

1-15 - Service destruction failed

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

Possible Causes

An exception thrown when destroying all invokers in the RegistryDirectory may trigger error 1-15.

Troubleshooting and Resolution Steps

This error is an internal Dubbo error. If you encounter it, you can create an issue on GitHub and provide the error message along with reproduction steps, and we will assist you in resolving the problem.

See also Dubbo Community

1-16 - Unsupported categories exist

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

Possible Causes

When there are changes in the registration center, the corresponding listener will be notified. If the category is invalid during the notification, it will result in unsupported categories existing.

Troubleshooting and Resolution Steps

This error is an internal Dubbo error. If you encounter it, you can create an issue on GitHub and provide the error information as well as reproduction steps, and we will assist you in resolving the issue.

1-17 - metadata Server failure

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

Possible Causes

There may be issues with the configuration of relevant parameters related to metadata, particularly metadataServiceProtocol and metadataServicePort.

Troubleshooting and Resolution Steps

Check if the failure occurs simultaneously with the absence of the metadata service port. If both occur, prioritize resolving the absence of the metadata service port. (1-18 FAQ)
Check whether there is a conflict with the metadataServicePort port number. If there is a conflict between the ports configured for the Provider and Consumer, it will cause the metadata Server to fail.

See also Configuration Reference Manual

1-18 - Metadata service port not provided

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

Possible Causes

This may be due to the metadataType being set to local mode, and there is an error in the metadataServicePort configuration.

Troubleshooting and Resolution Steps

Check the metadataType attribute value on the Provider side.
Check if the metadataServicePort configuration on the Provider side is correct, paying particular attention to whether there is a conflict with other application ports.

Also Refer To Configuration Reference Manual

1-19 - K8S Listener Exception

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

Possible Causes

The custom resource type in K8S has been modified or removed by the container.
The K8S container is disconnected from the service.

Troubleshooting and Resolution Steps

Check if the custom resource type and configuration are correct. For syntax or formatting, please refer to the official K8S documentation.
Check if the network is functioning properly or if the port mapping is correct.

1-20 - K8S Pod does not exist

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

Possible Causes

Controller is Pending.
The Pod may not exist or has been removed by the container.

Troubleshooting and Resolution Steps

You can analyze the stack information using some third-party tools or jstack [PID] > jstack.log to locate the issue.

1-21 - No available services in K8S

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

Possible Causes

The current service has not been loaded properly.
The configured Pod does not actually exist in the current instance service.

Troubleshooting and Resolution Steps

You can analyze stack information through some third-party tools or by using jstack [PID] > jstack.log to locate the issue.

1-22 - Incorrect K8S configuration address

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

Possible Causes

The K8S URL configuration is incorrect, preventing normal access.

Troubleshooting and Resolution Steps

Check the K8S URL configuration information and ensure that the port mapping is also accessible.

1-26 - xDS Certificate Generation Failure

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

Possible Causes

The system may not support the algorithms secp256r1 and RSA for generating certificates.

Troubleshooting and Resolution Steps

Check whether the operating system supports the secp256r1 and RSA algorithms. You may need to download the corresponding dll files or lib.

1-27 - K8S Listening Exception

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

Possible Causes

The system may not support the secp256r1 and RSA algorithms for certificate generation.

Troubleshooting and Resolution Steps

Check if the operating system supports the secp256r1 and RSA algorithms. Required DLL files or libraries need to be downloaded.

1-28 - xDS Stub Error

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

Possible Causes

The current pod is down or has crashed.

Troubleshooting and Resolution Steps

You can analyze the stack information using some third-party tools or jstack [PID] > jstack.log to locate the issue.

1-29 - xDS File Read Failed

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

Possible Causes

Network disconnection or the target file is corrupted at this time.

Troubleshooting and Resolution Steps

Check if the network is normal.
You can analyze the stack information using some third-party tools or jstack [PID] > jstack.log for diagnosis.

1-30 - xDS Request Failed

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

Possible Causes

The versions may be inconsistent or incompatible.
Timeout while reading data.
Issues with parameter configuration.

Troubleshooting and Resolution Steps

Adapt according to the introduction provided by the third-party official website.
Confirm whether the timeout setting is too short or there are issues on the server side.
Check whether the port mapping is correct.

1-31 - xDS Response Failure

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

Possible Causes

The client service has lost connection to the server.
The server is unavailable or offline.

Troubleshooting and Resolution Steps

Check whether the server is offline or if the client’s network is disconnected.
Verify that the server service is running normally and can be accessed via network interface requests.

1-32 - xDS Channel initialization failure

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

Possible Causes

The versions may be inconsistent or incompatible.
Timeout while reading data.
There may be issues with parameter configuration.

Troubleshooting and Resolution Steps

Adapt according to the introduction from the third-party official website.
Confirm whether the timeout is set too short or if there are issues on the server side.
Check whether the port mapping relationship is correct.

1-33 - xDS service discovery initialization failure

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

Possible Causes

Incorrect address configuration of the registry in xDS mode.
Firewalls and third-party protection software preventing external connections.

Troubleshooting and Resolution Steps

Check if the xDS configuration is correct and verify the status of Istio.
Check the firewall configuration or perform basic tests using the ping command in cmd.

1-34 - Error occurred while parsing xDS

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

Possible Causes

There is an error in the content of the xDS protocol.

Troubleshooting and Resolution Steps

You can locate the cause based on the Endpoints List printed in the stack trace.

1-35 - ZK Exception

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

Possible Causes

Unable to connect to ZK or connection timeout.
ZNode already exists at the time of creation.

Troubleshooting and Resolution Steps

Check if the ZK configuration IP and port number are correct. You can use third-party tools like ZooInspector for connection testing.
Based on the stack trace, determine the ZNode information to see if the current node can be cleaned up.

1-36 - Unknown Exception

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

Possible Causes

The meaning of this error code has been adjusted. For the errors associated with this error code in Dubbo versions 3.1.4, 3.2.0-beta.3 and prior, please refer to error code 99-0.

Troubleshooting and Resolution Steps

(This error code currently has no information)

1-37 - Nacos Exception

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

Possible Causes

Nacos configuration information is not properly configured.

Troubleshooting and Resolution Steps

Check if the IP and port number for configuring Nacos are correct. If Nacos’s security authentication is enabled, check if the username and password configuration are correct.

1-38 - Socket Connection Exception

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

Possible Causes

Connection was refused.
Connection has been closed.

Troubleshooting and Resolution Steps

You can use some third-party tools or jstack [PID] > jstack.log to analyze the stack information for diagnostics.

1-39 - Failed to retrieve metadata

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

Possible Causes

The metadata center has been disconnected from the application service.
The data of the metadata center has been modified or corrupted.

Troubleshooting and Resolution Steps

Check if network communication is normal; you can use simple cmd commands for testing, such as ping, etc.
Use third-party tools to establish a connection and view the content.

1-40 - Route waiting time is too long

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

Possible Causes

The routing calculation takes too long, causing the address notification to not wait for a suitable time to perform the address update.

Troubleshooting and Resolution Steps

Check the application QPS; if the QPS is very high, this is expected logging.
Check the implementation of custom routing to identify any abnormal implementations, such as deadlocks or infinite loops.
You can use some third-party tools or jstack [PID] > jstack.log to analyze stack information for diagnosis.

1-41 - Istio Exception

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

Possible Causes

Failed to obtain the Istio configuration file.

Troubleshooting and Resolution Steps

Check if the application is deployed in a Kubernetes Pod environment, as VM deployment is currently not supported.

1-42 - Low Version Services Exist in Nacos

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

Possible Causes

The Nacos registry is subscribed to older version services, usually caused by the server-side Dubbo version being lower than 2.7.3.

Troubleshooting and Resolution Steps

Upgrade the server to the latest stable version.

1 - Registry Center Layer on Apache Dubbo

1-1 - Invalid Address

Possible Causes

Troubleshooting and Resolution Steps

1-3 - URL destruction failure

Possible Causes

Troubleshooting and Resolution Steps

1-4 - Empty Address

Possible Causes

Troubleshooting and Resolution Steps

1-5 - Received URL with no parameters

Possible Causes

Troubleshooting and Resolution Steps

1-6 - Error clearing URL cache

Possible Reasons

Troubleshooting and Resolution Steps

1-7 - Notification registration event failure

Possible Causes

Troubleshooting and Resolution Steps

1-8 - Failure to unregister (unsubscribe) address during destruction

Possible Reasons

Troubleshooting and Resolution Steps

1-9 - Failure to read and write the registry service cache

Possible Causes

1-10 - Failed to read and write the service cache of the registry

Possible Causes

Troubleshooting and Resolution Steps

1-11 - Service instance registration failure

Possible Causes

Troubleshooting and Resolution Steps

1-12 - Instances of "Registered Service" have been destroyed

Possible Causes

Troubleshooting and Resolution Steps

1-13 - Failed to execute retry task

Possible Causes

Troubleshooting and Resolution Steps

1-14 - Dynamic Configuration Recognition Failure

Possible Causes

Troubleshooting and Resolution Steps

See Also

1-15 - Service destruction failed

Possible Causes

Troubleshooting and Resolution Steps

1-16 - Unsupported categories exist

Possible Causes

Troubleshooting and Resolution Steps

1-17 - metadata Server failure

Possible Causes

Troubleshooting and Resolution Steps

1-18 - Metadata service port not provided

Possible Causes

Troubleshooting and Resolution Steps

1-19 - K8S Listener Exception

Possible Causes

Troubleshooting and Resolution Steps

1-20 - K8S Pod does not exist

Possible Causes

Troubleshooting and Resolution Steps

1-21 - No available services in K8S

Possible Causes

Troubleshooting and Resolution Steps

1-22 - Incorrect K8S configuration address

Possible Causes

Troubleshooting and Resolution Steps

1-26 - xDS Certificate Generation Failure

Possible Causes

Troubleshooting and Resolution Steps

1-27 - K8S Listening Exception

Possible Causes

Troubleshooting and Resolution Steps

1-28 - xDS Stub Error

Possible Causes

Troubleshooting and Resolution Steps

1-29 - xDS File Read Failed

Possible Causes

Troubleshooting and Resolution Steps

1-30 - xDS Request Failed

Possible Causes

Troubleshooting and Resolution Steps

1-31 - xDS Response Failure