| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – 3 - Proxy</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/</link><description>Recent content in 3 - Proxy 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/3/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: 3-1 - Failed to convert address to Invoker</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/1/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/1/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li> |
| <p>The protocol configured on the client side does not match the protocol configured on the server side. (For example, the protocol configured by the client is the Dubbo protocol, but the server can only provide services of the Rest protocol.)</p> |
| </li> |
| <li> |
| <p>The registration center (or configuration center) is unreliable and pushes illegal data.</p> |
| </li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check the protocol configuration of both the provider and the consumer.</li> |
| <li>Update the version of the registry.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 3-2 - Publish or push service failed</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/2/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/2/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The registration center cannot be connected.</li> |
| <li>The registration center cannot provide external services.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Whether the service and registration center network is normal.</li> |
| <li>Whether the registration center starts normally and can be connected through third-party tools.</li> |
| <li>Whether there is a version compatibility problem between the version referenced by the service and the version of the registration center.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 3-3 - Failed to generate bytecode via Javassist</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/3/</guid><description> |
| <h2 id="reminder">Reminder</h2> |
| <p>The meaning of this error code has been adjusted. If you are looking for information of this error code in Dubbo versions prior than (or equal) 3.1.4 or 3.2.0-beta.3, head to <a href="https://dubbo.apache.org/zh-cn/overview/mannual/java-sdk/faq/3/8/">3-8</a>.</p> |
| <p>(This error code is currently absent.)</p> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 3-4 - Client sending request timed out</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/4/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/4/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The number of client connections is too high, the response is slow, and the request cannot be sent to the server in time.</li> |
| <li>Some reasons for the network.</li> |
| </ol> |
| <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: 3-5 - An exception occurred in the asynchronous response</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/5/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/5/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The business logic does have a runtime exception.</li> |
| <li>The connection is refused due to network reasons.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>For the business code, please trace back and check according to the prompt line of the stack.</li> |
| <li>Check whether the network of the service provider is normal.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 3-6 - An exception occurred in the proxy execution service</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/6/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/6/</guid><description> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The current service parameters have been displayed as <code>deprecated</code>.</li> |
| <li>This reminder may appear for generic declaration classes.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Confirm whether there is a display parameter <code>deprecated=true</code> in the URL</li> |
| <li>If this error occurs in the generic declaration class, it will try to create a proxy without the actual interface class.</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item><item><title>Docs3-V2: 3-7 - Server response timed out</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/7/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/7/</guid><description> |
| <p>The server did not get a response within the time set by the client.</p> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>The business processing logic of the server is complex and cannot respond within the effective time.</li> |
| <li>The connection between the server and the client is disconnected, and the network packet is lost.</li> |
| <li>The server load is too high.</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>Check whether there is indeed a performance bottleneck in the business processing capability of the server.</li> |
| <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: 3-8 - Proxy Failure</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/8/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/faq/3/8/</guid><description> |
| <p>Failed to generate dynamic proxy.</p> |
| <h2 id="possible-reason">Possible Reason</h2> |
| <ol> |
| <li>There is dynamic class loading</li> |
| <li>Class format exception</li> |
| </ol> |
| <h2 id="troubleshooting-and-resolution-steps">Troubleshooting and resolution steps</h2> |
| <ol> |
| <li>If <code>Fallback to use JDK proxy success</code> is displayed in the log, |
| It means that Dubbo has successfully created a dynamic proxy after automatically falling back to the JDK proxy. If the program is running normally, you can ignore it</li> |
| <li>If the log shows <code>Fallback to use JDK proxy is also failed</code>, |
| Please check whether the corresponding class loading is normal according to the exception stack information, you can use tools such as arthas to assist in troubleshooting</li> |
| </ol> |
| <p style="margin-top: 3rem;"> </p></description></item></channel></rss> |
