| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – 0 - Common</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/</link><description>Recent content in 0 - Common 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/0/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: 0-1 - thread pool resource exhausted</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/1/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/1/</guid><description> |
| <p>The server&rsquo;s thread resources are exhausted. |
| By default, the number of business threads on the Dubbo server is 200. If the number of concurrent requests exceeds 200, new requests will be rejected and this error will be thrown.</p> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The amount of concurrent requests from the Consumer is too large, causing the number of threads created on the Provider to exceed the limit.</li> |
| <li>It is possible that when the Provider side executes the business, the thread is blocked because the business calls the external application interface, which makes the thread pool unable to recycle the thread.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ul> |
| <li>Enable Dubbo&rsquo;s access log function to check whether there are a large number of calls to RPC services in a short period of time.</li> |
| <li>Check the status of each thread in the thread pool through the <code>jps</code> and <code>jstack</code> instructions to see if there is any business calling the external application interface to cause blocking.</li> |
| <li>If the amount of concurrent requests from the Consumer is too large, then adjust the <code>dubbo.provider.threads</code> parameter on the Provider side to increase the number of Dubbo thread pools.</li> |
| <li>If the QPS of the Provider business is too large to be handled by the current number of servers, then increase the number of Provider-side servers so that more servers can share the pressure.</li> |
| </ul> |
| <blockquote> |
| <p>The FAQ page of this error code refers to <a href="https://github.com/StabilityMan/StabilityGuide/blob/master/docs/diagnosis/plugin/rpc/%E7%B3%BB%E7%BB%9F%E7%A8%B3%E5%AE%9A%E6%80%A7%E2%80%94%E2%80%94Dubbo%E5%B8%B8%E8%A7%81%E9%94%99%E8%AF%AF%E5%8F%8A%E8%A7%A3%E5%86%B3%E6%96%B9%E6%B3%95.md">&ldquo;Dubbo Common Errors and Solutions&rdquo;</a>. |
| Articles cited are compiled under license <a href="http://creativecommons.org/licenses/by/4.0/">CC-BY-4.0</a>. Thanks to the original author here.</p> |
| </blockquote></description></item><item><title>Docs3-V2: 0-2 - Illegal property value</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/2/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/2/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>This hint means that the value configured by the user does not match the data type required by the attribute itself. For example, the <code>dubbo.comsumer.threads</code> attribute can only accept numeric attributes, but the value entered by the user is mixed with letters.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>According to the <a href="../../../reference-manual/config/properties">Configuration Item Reference Manual</a>, find the wrong configuration item, check the type specified by the item, and check whether there is a type inconsistency.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-3 - Unable to access cache path</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/3/</guid><description> |
| <p>Other modules reuse the file-based caching mechanism of the Common layer (currently the metadata module), and the file caching mechanism of the Common layer cannot access the directory it specifies.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>2022-08-29 00:35:00,189 ERROR [org.apache.dubbo.common.cache.FileCacheStoreFactory:?] - [DUBBO] Cache store path can&#39;t be created: , dubbo version: , current host: 10.0.1.1 , error code: 0-3. This may be caused by inaccessible of cache path, go to https://dubbo.apache.org/faq/0/3 to find instructions. |
| </span></span><span style="display:flex;"><span>java.nio.file.FileAlreadyExistsException: [Path] |
| </span></span><span style="display:flex;"><span>at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:87) |
| </span></span><span style="display:flex;"><span>at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) |
| </span></span><span style="display:flex;"><span>at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) |
| </span></span><span style="display:flex;"><span>at java.base/sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:521) |
| </span></span><span style="display:flex;"><span>at java.base/java.nio.file.Files.createDirectory(Files.java:700) |
| </span></span><span style="display:flex;"><span>at java.base/java.nio.file.Files.createAndCheckIsDirectory(Files.java:807) |
| </span></span><span style="display:flex;"><span>at java.base/java.nio.file.Files.createDirectories(Files.java:753) |
| </span></span><span style="display:flex;"><span>at org.apache.dubbo.common.cache.FileCacheStoreFactory.getInstance(FileCacheStoreFactory.java:90) |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><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> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>According to the actual exception shown below, find the directory that cannot be accessed, and determine its file access permission.</li> |
| <li>Determine whether other Dubbo instances are accessing this path.</li> |
| <li>Try to configure <strong>Java System Property (Java system properties configured with -D)</strong> <code>dubbo.meta.cache.filePath</code> and <code>dubbo.mapping.cache.filePath</code>, specify it as a current user can completely under the control directory.</li> |
| </ol></description></item><item><title>Docs3-V2: 0-4 - cache entry exceeded</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/4/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/4/</guid><description> |
| <p>Other modules reuse the common layer&rsquo;s file-based caching mechanism (currently the metadata module), and the common layer&rsquo;s file caching mechanism &ldquo;sees&rdquo; that the entry limit is exceeded.</p> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>User improperly configured <strong>Java System Property</strong> (Java system property configured with -D) <code>dubbo.mapping.cache.entrySize</code> or <code>dubbo.meta.cache.entrySize</code></p> |
| <p><strong>Defaults</strong></p> |
| <style> |
| .sheet-border, .sheet-border tr, .sheet-border tr td { |
| border-width: 1px; |
| border-color: black; |
| text-align: center; |
| } |
| .sheet-border tr td { |
| height: 48px; |
| width: 83px; |
| border-style: solid; |
| padding: 0.6rem 0.6rem; |
| } |
| .sheet-header td { |
| font-weight: bold; |
| background: #cccccc; |
| } |
| </style> |
| <table class="sheet-border"> |
| <tr class="sheet-header"> |
| <td>dubbo.mapping.cache.entrySize</td> |
| <td>dubbo.meta.cache.entrySize</td> |
| </tr> |
| <tr> |
| <td>10000</td> |
| <td>100</td> |
| </tr> |
| </table> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Try reconfiguring the above <strong>Java System Property (Java System Property configured with -D)</strong>.</li> |
| <li>If these <strong>System Property</strong> are not configured, please go to <a href="https://github.com/apache/dubbo/issues">GitHub Issue Tracker</a> to issue an Issue.</li> |
| </ol></description></item><item><title>Docs3-V2: 0-5 - Cache file size exceeded</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/5/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/5/</guid><description> |
| <p>Other modules reuse the file-based caching mechanism of the Common layer (currently the metadata module), and the file caching mechanism of the Common layer &ldquo;discovers&rdquo; that the file size exceeds the limit.</p> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The user has unreasonably configured the Java System Property (the Java system property configured with -D) <code>dubbo.mapping.cache.maxFileSize</code> or <code>dubbo.meta.cache.maxFileSize</code></li> |
| <li>The cache file is corrupted due to file system or disk errors.</li> |
| </ol> |
| <blockquote> |
| <p><code>dubbo.mapping.cache.maxFileSize</code> and <code>dubbo.meta.cache.maxFileSize</code> do not show default values, |
| The default value of the maximum file size found according to the logic of <code>org.apache.dubbo.common.cache.FileCacheStore.LimitedLengthBufferedWriter</code> is: <code>Long.MAX_VALUE</code> ( 2<sup>63</sup>-1 ).</p> |
| </blockquote> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Try reconfiguring the above <strong>Java System Property (Java System Property configured with -D)</strong>.</li> |
| <li>Delete the cache folder and restart <strong>Provider</strong> and <strong>Consumer</strong> (the location of the cache folder is usually <code>~/.dubbo</code>. If <code>dubbo.meta.cache.filePath</code> and <code>dubbo.mapping</code> are configured .cache.filePath` is that path).</li> |
| <li>If these <strong>System Property</strong> are not configured, please go to <a href="https://github.com/apache/dubbo/issues">GitHub Issue Tracker</a> to issue an Issue.</li> |
| </ol></description></item><item><title>Docs3-V2: 0-6 - Thread interruption exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/6/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/6/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When a running thread is in <code>wait, sleep, join</code>, it is explicitly called <code>interrupt()</code></p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>After a normal running thread calls the <code>interrupt()</code> method, the interrupt status of the current thread will be set to true, but the execution of the thread will not be affected. |
| You can operate according to the actual situation or check whether the business code is used incorrectly.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-7 - Reflection class not found</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/7/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/7/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>Generally, when <code>Class.forName(className)</code> executes this method, the current class of <code>className</code> cannot be found.</li> |
| <li>The business code shows that the current <code>className</code> class is excluded, so it is not found when loading.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check whether <code>className</code> exists in <code>Class.forName(className)</code>.</li> |
| <li>Check the business code to see whether some classes or packages have been excluded by using the configuration or scanning annotation <code>exclude</code>.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-8 - reflection failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/8/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/8/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When a method is called by reflection, the correct parameter type value is not set for the current method, that is, the parameter type does not match.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Check for matching type values that are not set correctly.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-9 - Failed to notify event</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/9/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/9/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>A custom listener that generated a runtime exception during processing.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Check the business class that implements the <code>org.apache.dubbo.rpc.ExporterListener</code> interface. There may be code logic errors in the implementation method.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-10 - The current call is no longer supported</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/10/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/10/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The currently called method may have been deprecated or declared <code>@Deprecated</code>, which does not affect the execution result.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Please use other alternative API methods.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-11 - Service stop failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/11/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/11/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The connection is not closed in time or the memory is insufficient, causing some exceptions when the service stops.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Close the connection after the response content is completed.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-12 - Unknown exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/12/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/12/</guid><description> |
| <p>Unknown exception, usually API usage or configuration exception</p> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>Such as: transcoding exception, unsupported encryption and decryption methods, etc.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>The business code line can be located according to the stack information.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-13 - An exception occurred in the metrics collector</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/13/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/13/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>An error occurred during the push process of the indicator data, the pushed server could not be connected or some configuration errors were made. Prometheus is currently supported.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Please refer to the configuration item reference manual<a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/config/properties/#metrics">configuration item reference manual</a>.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-14 - Monitoring exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/14/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/14/</guid><description> |
| <p>It is used to count the number of RPC calls and the call time. The extension interface is MonitorFactory, and the corresponding implementation class is DubboMonitorFactroy.</p> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>Users can implement the MonitorFactory extension interface of this layer to implement custom monitoring statistics strategies. |
| In the implementation class of the custom monitoring statistics strategy, an exception occurred during business runtime.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Check the business class of <code>org.apache.dubbo.monitor.MonitorFactory</code> interface, there may be code logic errors in the implementation method.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-15 - An exception occurred while loading the extension class</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/15/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/15/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The <code>clazz</code> class does not implement the interface class of the current extension point.</li> |
| <li>The extension may be an interface or not exist.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check the extension class declaration, and there is no matching extension implementation class.</li> |
| <li>The extension implementation class needs to implement the extension point interface class and method.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-16 - No actuators available</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/16/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/16/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The internal executor is not available and null is returned at this time.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>No need to intervene, dubbo will execute the <code>createExecutorIfAbsent</code> method internally to construct a new executor.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-17 - Actuator encountered an unknown exception while shutting down</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/17/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/17/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>A custom executor may be used, and an exception was generated when writing the destruction method.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Check whether <code>org.apache.dubbo.common.threadpool.manager.ExecutorRepository</code> is custom implemented, and check the custom <code>shutdown</code> method.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-18 - thread pool executor is misused</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/18/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The number of threads is customized, and an unknown exception occurs inside the system.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <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: 0-19 - An exception occurred while processing the task</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/19/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/19/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The custom business class processing logic is improper.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <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: 0-20 - An exception occurred while storing stack information</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/20/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/20/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The JVM has set the parameter <code>-XX:+DisableAttachMechanism</code></li> |
| <li>Set a stack dump path that does not exist in the system. If it does not exist, the system will try to create it. A <code>SecurityException</code> occurs during creation. |
| May not have permission.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check whether the JVM has set the above parameters.</li> |
| <li>Check whether the account currently starting the service has permission to create folders.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-21 - Too many instances built</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/21/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/21/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>Generally, it means that <code>org.apache.dubbo.common.timer.HashedWheelTimer</code> creates too many instances.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>It does not affect the construction of the instance, and there may be a risk of memory leaks.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-22 - I/O stream exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/22/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/22/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>Read a local file that is no longer available.</li> |
| <li>Attempt to read/write the file but do not have permission.</li> |
| <li>An attempt was made to write a file but disk space is no longer available.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check if the local file exists.</li> |
| <li>Check the file permissions.</li> |
| <li>Check the disk space.</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: 0-23 - Serialized data conversion exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/23/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>There is a circular reference in the data to be serialized, resulting in a stack overflow.</li> |
| <li>The version of the referenced jar package is low or there is a compatibility problem.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>If using FastJson, remove <code>SerializerFeature.DisableCircularReferenceDetect</code></li> |
| <li>Check or upgrade the version to try.</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: 0-24 - Override field value exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/24/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/24/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <ol> |
| <li>The entity class does not have a setter/getter method.</li> |
| <li>There may be nested attributes.</li> |
| </ol> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <ol> |
| <li>Check the entity class and set the setter/getter method.</li> |
| <li>According to the stack information, check whether nested annotations are used.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-25 - Error loading map</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/25/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/25/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>Insufficient file access rights</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Check file permissions. |
| 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: 0-26 - Warning message when metadata is published to the service</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/26/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/26/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>When the metadata stores the mapping relationship between the interface and the application, the reminder message displayed.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Generally, it can be analyzed according to the stack information, or it can not be processed.</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 0-27 - Thread pool isolation configuration exception</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/27/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/0/27/</guid><description> |
| <h3 id="possible-reason">Possible Reason</h3> |
| <p>The thread pool isolation capability of the application is not enabled, but the isolated thread pool information is configured in <code>ServiceConfig</code>.</p> |
| <h3 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h3> |
| <p>Configure and enable the thread pool isolation capability of the application: <code>dubbo.application.executor-management-mode=isolation</code></p> |
| <p style="margin-top: 3rem;"> </p></description></item></channel></rss> |
