| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – 1 - Registry</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/</link><description>Recent content in 1 - Registry on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: 1-1 - Address Illegal</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/1/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/1/</guid><description> |
| <p>This log can be ignored, service version or grouping mismatch. Appears only in the zookeeper registry, this check has been removed in version 3.1.7.</p> |
| <h3 id="possible-reason">possible reason</h3> |
| <ol> |
| <li>The <code>service.group</code> configured on the Provider side does not match the <code>reference.group</code> configured on the Consumer side (that is, the configuration of the service group).</li> |
| <li>The <code>service.version</code> configured on the Provider side does not match the <code>reference.version</code> configured on the Consumer side (that is, the configuration of the service version).</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Can be ignored, this check has been removed in version 3.1.7.</p></description></item><item><title>Docs3-V2: 1-3 - URL destruction failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/3/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When <code>FrameworkExecutorRepository</code> is destroyed, calling <code>CacheableFailbackRegistry.evictURLCache</code> will cause the destruction to fail and generate an error code.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <blockquote> |
| <p>See also the <a href="../../../reference-manual/config/properties">Configuration Items Reference Manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-4 - Empty address</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/4/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/4/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>Errors 1-4 in registry.integration.RegistryDirectory are caused by the null invokerUrls in the refreshInvoker process, which can be ignored.</li> |
| <li>The 1-4 errors in registry.support.CacheableFailbackRegistry may be caused by the mismatch between consumer and provider, and the &ldquo;null protection&rdquo; is turned off.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Make sure that the service group configurations on the Provider and Consumer side correspond.</li> |
| <li>Make sure that the service version configurations on the Provider and Consumer side correspond.</li> |
| <li>Check whether <code>enable-empty-protection</code> of the registration center is true (the default is true).</li> |
| </ol> |
| <blockquote> |
| <p>see also |
| <a href="../../../reference-manual/config/properties">Configuration item reference manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-5 - URL received without any parameters</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/5/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/5/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When calling <code>CacheableFailbackRegistry.toUrlsWithoutEmpty</code>, if there is a provider in <code>Collection&lt;String&gt;providers</code> that does not have any parameters, the URL without any parameters will be received.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>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 steps to reproduce it. We will help you solve the problem.</p> |
| <blockquote> |
| <p>see also |
| <a href="https://github.com/apache/dubbo">Dubbo Community</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-6 - Error clearing URL cache</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/6/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/6/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>An error while clearing the url cache in <code>CacheableFailbackRegistry.RemovalTask</code> will trigger an error in clearing the URL cache.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>This error is an internal error of Dubbo, if you encounter it, you can create <strong>issues</strong> on github and provide the error information and steps to reproduce, we will help you solve the problem.</p> |
| <blockquote> |
| <p>see also |
| <a href="https://github.com/apache/dubbo">Dubbo Community</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-7 - Notification registration event failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/7/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/7/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>When applied to related platforms based on the xDS protocol, when metadata is updated, consumers need to be notified. If a consumer is offline, the notification will fail and the listener of the corresponding consumer will be removed.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <blockquote> |
| <p>see also |
| <a href="https://dubbo.apache.org/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry">Registration Center - Configuration Item Reference Manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-8 - Unregister (unsubscribe) address failed on destroy</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/8/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/8/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>An error may occur when the consumer logs out or unsubscribes due to the downtime of the registration center.</li> |
| <li>It may be that the corresponding provider has not been released successfully.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check whether the registration center is running normally.</li> |
| <li>Check whether the provider is released successfully.</li> |
| <li>Check whether the provider’s registry-related parameters such as <code>registry</code> <code>config-center</code> <code>metadata-report</code> are configured correctly.</li> |
| </ol> |
| <blockquote> |
| <p>see also |
| <a href="../../../reference-manual/config/properties">Configuration item reference manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-9 - Failed to read and write registry service cache</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/9/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/9/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>Multiple Dubbo processes (or other Java processes) use the same cache file.</li> |
| <li>Due to the file system permission problem of the directory where the cache file is located, reading and writing fails.</li> |
| <li>The value of <code>dubbo.registry.file</code> is entered incorrectly.</li> |
| <li>Accidentally specify two registries to use the same file store.</li> |
| </ol> |
| <blockquote> |
| <p><strong>Hint:</strong> |
| If <code>dubbo.registry.file</code> is not specified, the registry service cache path defaults to the <code>~/.dubbo</code> directory |
| (where <code>~</code> is the user&rsquo;s HOME directory)</p> |
| </blockquote> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check the value of <code>dubbo.registry.file</code> for typos.</li> |
| <li>Check whether other processes use the same cache file.</li> |
| <li>If <code>dubbo.registry.file</code> is specified, check its permissions in the file system.</li> |
| <li>Check whether the situation of &ldquo;two registration centers use the same file storage&rdquo; occurs, and adjust if it occurs.</li> |
| </ol> |
| <blockquote> |
| <p>see also |
| <a href="https://dubbo.apache.org/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry">Reference Manual for Registry Configuration Items</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-10 - Failed to read and write registry service cache</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/10/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/10/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>Multiple Dubbo processes use the same cache file.</li> |
| <li>In the case of multiple registries, multiple registries are specified to use the same file storage.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>This error often occurs with errors 1-9. Check whether multiple Dubbo processes use the same cache file or specify multiple registries to use the same cache file.</p> |
| <blockquote> |
| <p>see also |
| <a href="https://dubbo.apache.org/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry">Reference Manual for Registry Configuration Items</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-11 - Registration service instance creation failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/11/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/11/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>It may be caused by Registry&rsquo;s SPI/IOC configuration error.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>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 steps to reproduce it. We will help you solve the problem.</p> |
| <blockquote> |
| <p>see also |
| <a href="https://github.com/apache/dubbo">Dubbo Community</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-12 - Instances of "Registry Service" have been destroyed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/12/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/12/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>During the graceful shutdown of Dubbo, unregister by calling <code>destroyAll</code> of <code>AbstractRegistryFactory</code>.</p> |
| <p>During the process of destroying the <code>unexport</code> of <code>Registryprotocol</code>, the <code>getRegistry</code> of <code>AbstractRegistryFactory</code> will be used to try to obtain the registry that has been destroyed, which leads to the destruction of all instances of the &ldquo;registry service&rdquo;.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <blockquote> |
| <p>see also |
| <a href="../../../reference-manual/config/properties">Configuration item reference manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-13 - Failed to execute task retry</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/13/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/13/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The registry is offline.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check if the registry is working properly.</li> |
| <li>Check whether the server where the registration center is located and its network are working normally.</li> |
| </ol></description></item><item><title>Docs3-V2: 1-14 - Dynamic configuration recognition failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/14/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/14/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When using the service management function of dubbo admin for dynamic configuration, if the content or format of the configuration file is incorrect, the content of the dynamic configuration cannot be parsed, resulting in 1-14 errors.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Please check whether the content or format of the dynamic configuration file is correct.</p> |
| <h3 id="see-also">See also</h3> |
| <blockquote> |
| <p><a href="../../../reference-manual/config/properties">Configuration Reference Manual</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-15 - Failed to destroy service</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/15/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/15/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>Throwing an exception while destroying all invokers in the RegistryDirectory may trigger errors 1-15.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>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 steps to reproduce it. We will help you solve the problem.</p> |
| <blockquote> |
| <p>See also <a href="https://github.com/apache/dubbo">Dubbo Community</a></p> |
| </blockquote></description></item><item><title>Docs3-V2: 1-16 - There are unsupported categories</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/16/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/16/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>When the registration center changes, the corresponding listener will be notified. If the category is illegal during notify, 1-16 errors will be generated.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>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 steps to reproduce it. We will help you solve the problem.</p> |
| <h2 id="dubbo-community">Dubbo Community</h2> |
| <p><a href="https://github.com/apache/dubbo">github</a></p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-17 - Metadata Server Failure</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/17/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/17/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>It may be that there is a problem with the parameter configuration of metadata, especially <code>metadataServiceProtocol</code> and <code>metadataServicePort</code>.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether it occurs at the same time as 1-18 error, if it occurs at the same time, first try to solve 1-18</li> |
| <li>Check whether the <code>metadataServicePort</code> port number conflicts. If the ports configured by Provider and Consumer are in conflict at the same time, a 1-17 error will be generated.</li> |
| </ol> |
| <h2 id="see-also">see also</h2> |
| <p><a href="../../../reference-manual/config/properties">Configuration item reference manual</a></p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-18 - metadata service port not provided</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/18/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>It may be that <code>metadataType</code> is in local mode, and <code>metadataServicePort</code> is configured incorrectly.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check the <code>metadataType</code> attribute value on the Provider side.</li> |
| <li>Check whether the configuration of <code>metadataServicePort</code> on the Provider side is correct, and pay special attention to whether there is any conflict with other application ports.</li> |
| </ol> |
| <h2 id="see-also">see also</h2> |
| <p><a href="../../../reference-manual/config/properties">Configuration item reference manual</a></p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-19 - K8S monitoring exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/19/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/19/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>K8S custom resource type, the configuration has been modified or removed by the container.</li> |
| <li>The K8S container is disconnected from the service.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the custom resource type is correctly configured. For syntax, please refer to the official documentation of K8S.</li> |
| <li>Check whether the network is normal or the port mapping is correct.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-20 - K8S Pod does not exist</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/20/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/20/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>Pods may not exist or have been removed by containers.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-21 - K8S No Service Available</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/21/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/21/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The current service is not loaded correctly.</li> |
| <li>The configured Pod does not exist in the current instance service.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-22 - K8S configuration address error</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/22/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/22/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The K8S url is configured incorrectly and cannot be accessed normally.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>Check the K8S url configuration information to ensure that the port mapping can also be accessed normally.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-23 - Unable to download files via url</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/23/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The url mapping file does not exist.</li> |
| <li>The URL cannot be connected.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the url mapping file exists.</li> |
| <li>Whether it can be accessed normally through a browser or other tools.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-24 - ZK startup exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/24/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/24/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>There is an incompatibility between the zk server version and the client version, and the connection cannot be made.</li> |
| <li>The zk service is not started normally or the firewall cannot provide external services.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Confirm that the client version is consistent with the server version.</li> |
| <li>zk can start normally or provide normal external services.</li> |
| </ol> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-25 - ZK destruction exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/25/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/25/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The current instance has been destroyed. |
| The network may be disconnected.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-26 - xDS certificate generation failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/26/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/26/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The system may not support algorithms <code>secp256r1</code> and <code>RSA</code> to generate certificates.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>Check if the operating system supports <code>secp256r1</code> and <code>RSA</code> algorithms. Need to download the dll file or lib for</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-27 - K8S monitoring exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/27/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/27/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The system may not support algorithms <code>secp256r1</code> and <code>RSA</code> to generate certificates.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>Check if the operating system supports <code>secp256r1</code> and <code>RSA</code> algorithms. Need to download the dll file or lib for</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-28 - xDS Stub Error</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/28/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/28/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The current pod may be down.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-29 - xDS failed to read file</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/29/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/29/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The network is disconnected or the target file is corrupted at this time.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Whether the network is normal.</li> |
| <li>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-30 - xDS request failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/30/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/30/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>Versions may be inconsistent or incompatible.</li> |
| <li>Timeout while reading data.</li> |
| <li>There is a problem with parameter configuration.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>It can be adapted according to the introduction of the third-party official website.</li> |
| <li>Check whether the timeout setting is too short or there is a problem on the server.</li> |
| <li>Check whether the port mapping relationship is correct.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-31 - xDS Response Failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/31/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/31/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The client service has disconnected from the server.</li> |
| <li>The server is unavailable or offline.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the server is offline or the network of the client is disconnected.</li> |
| <li>Check whether the service on the server side is normal, and the interface request can be made through the network.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-32 - xDS Channel initialization failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/32/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/32/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>Versions may be inconsistent or incompatible.</li> |
| <li>Timeout while reading data.</li> |
| <li>There is a problem with parameter configuration.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>It can be adapted according to the introduction of the third-party official website.</li> |
| <li>Check whether the timeout setting is too short or there is a problem on the server.</li> |
| <li>Check whether the port mapping relationship is correct.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-33 - xDS service discovery initialization failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/33/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/33/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The address configuration of the registration center in xDS mode is wrong.</li> |
| <li>The firewall and third-party protection software make it impossible to provide external connections.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the xDS configuration is correct and whether the Istio status is normal.</li> |
| <li>Check the firewall configuration or use the <code>ping</code> command of cmd for basic detection.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-34 - Error parsing xDS</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/34/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/34/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>There is an error in the xDS protocol content.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>The cause can be located according to the Endpoints List printed by the stack.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-35 - ZK Anomaly</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/35/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/35/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>ZK cannot connect or the connection times out.</li> |
| <li>The ZNode already exists at the time of creation.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether ZK configuration IP and port number are correct. Connection testing can be done using the third-party tool ZooInspector</li> |
| <li>According to the stack reminder ZNode information, judge whether the current node can be cleaned up.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-36 - Unknown exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/36/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/36/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-37 - Nacos Anomaly</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/37/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/37/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>Nacos configuration information is not configured correctly.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>Check whether the ip and port number configured for Nacos are correct. If the security authentication of Nacos is enabled, check whether the user name and password are configured correctly.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-38 - Socket connection exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/38/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/38/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>Connection refused.</li> |
| <li>The connection has been closed.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <p>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-39 - Failed to fetch metadata</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/39/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/39/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>Metadata Center has been disconnected from App Service.</li> |
| <li>The data in the metadata center may have been modified.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the network communication is normal, you can use some simple cmd commands to detect, such as <code>ping</code> and so on.</li> |
| <li>Connect and view content through third-party tools.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-40 - Route waiting too long</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/40/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/40/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>The route calculation time is too long, so the address notification cannot wait for an appropriate time to update the address.</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check the application QPS, if the QPS is very high, this is the expected log</li> |
| <li>Check the implementation of custom routes, and check whether there are abnormal implementations, such as deadlocks, infinite loops, etc.</li> |
| <li>You can use some third-party tools or <code>jstack [PID] &gt; jstack.log</code> to analyze the stack information and locate it.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-41 - Istio exceptions</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/41/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/41/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <p>Failed to fetch configuration file for istio</p> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether the application is deployed in the Kubernetes Pod environment, currently does not support VM deployment</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 1-42 - Nacos has a low version service</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/42/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/1/42/</guid><description> |
| <h3 id="possible-reason">possible reason</h3> |
| <p>The Nacos registry has subscribed to an old version of the service, usually because the Dubbo version on the server side is lower than 2.7.3.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Upgrade the server to the latest stable version.</p></description></item></channel></rss> |
