Tag Archives: dubbo

[Solved] Dubbo Error: No provider available for the service xxx from registry localhost:9090

Dubbo operates as follows:

One service provider, one service consumer, service provider configuration parameter Dubbo.application.Name = AA, service consumer configuration parameter dubbo.cloud.subscribed-service=bb. Start the service provider first, then start the service consumer, then call the consumer interface to prompt the exception.

Error content:

org.apache.dubbo.rpc.RpcException: Failed to invoke the method sayHello in the service xxx. No provider available for the service xxx from registry localhost:9090 on the consumer [ip] using the dubbo version 2.7.3. Please check if the providers have been started and registered.

Cause of problem: due to negligence, the service provider Dubbo application. The value of name is consistent with the service consumer configuration Dubbo cloud. The value of the subscribed service is written inconsistently, resulting in the consumer unable to find the service provider according to the configuration at startup.

Solution: Modify the parameter value of the service consumer Dubbo.cloud.subscribed-service to the service provider Dubbo.application.Name.

There are many reasons for this problem. There are also some reasons on the Internet that are caused by the inconsistency between the versions of Dubbo and spring cloud. If the parameter configuration is not abnormal but still reports an error, it is recommended to modify the versions of spring boot, spring cloud and Dubbo. The versions of spring boot, spring cloud and Dubbo should be compatible.

[Solved] Dubbo uses filter error: No such extension consumerStaticFilter for filter/com.alibaba.dubbo.rpc.Filter

Dubbo can use filter to implement a filter similar to the Tomcat filter

Realize 1. Interface request time monitoring. 2. Print input/output log (the output log is determined by the application itself)

An error occurred during the configuration

No such extension consumerStaticFilter for filter/com.alibaba.dubbo.rpc.Filter

at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:102)

Ask experienced students in the company to know the reason

When configuring & lt; dubbo:provider filter=”DubboExceptionFilter”>& lt;/ dubbo:provider>

The value of dubboexceptionfilter is not a spring bean. Instead, the following file contents need to be configured in the meta-inf/Dubbo/com.alibaba.dubbo.rpc.filter file:

DubboExceptionFilter=com.xxx.common.DubboRequestFilter

Create another related type and implement the com.alibaba.dubbo.rpc.filter interface

 

public DubboRequestFilter implements com.alibaba.dubbo.rpc.Filter{

}

This mechanism is the Java Service provider interface, Java specification. In this way, it is not necessary to configure a complete class during configuration

Dubbo startup error failed to bind nettyserver on

Dubbo error reporting

 

 

 

When I started the project today, I turned off the custom service

<dubbo:consumer check="false"/>

And turned off spring’s elastic job

<!--<import resource="cloud-elastic-job.xml"/>-->

But I still reported an error. I looked at the error code because

The Dubbo service of dev IP needs to occupy port 12500, but my local port 12500 is occupied. An error is reported when mapping to my local port 12500. Just kill it

 

Find which process is using the local 12500 port

lsof -i tcp:12500

> lsof -i tcp:12500

>>

>>

Dubbo learning — import eclipse exception unbound classpath container (2)

Dubbo learning — import eclipse exception unbound classpath container (2)

Tags (space separated): Dubbo eclipse

[TOC]

1. Import eclipse

Import Dubbo to eclipse using the buildship plug-in

After success, there is a red exclamation mark on all projects, and the error is as follows:

Build path	Build Path Problem
Unbound classpath container: 'JRE System Library [JavaSE-1.5]' in project 'dubbo-xxxx'

2. Solutions

Window -> Preferences -> Java -> Installed JREs

Add a new standard JVM, define the JRE name as javase-1.5, and save it