Dubbo Demo Running Successfully and Update Native Maven Repositories

最新推荐文章于 2024-03-13 22:40:57 发布
最新推荐文章于 2024-03-13 22:40:57 发布
阅读量628 收藏
点赞数
分类专栏： Java JavaEE Spring Configuration Error Solution
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/xiuye2015/article/details/79491358
版权
Java 同时被 3 个专栏收录
297 篇文章 1 订阅
订阅专栏
Error Solution
140 篇文章 0 订阅
订阅专栏
JavaEE
94 篇文章 0 订阅
订阅专栏 
package com.xiuye.service;

public interface DemoService {

	String hello(String str);

}


package com.xiuye.provider;

import java.text.SimpleDateFormat;
import java.util.Date;

import com.xiuye.service.DemoService;
import com.alibaba.dubbo.rpc.RpcContext;

public class DemoServiceImpl implements DemoService{


	@Override
	public String hello(String name) {
		System.out.println("[" + new SimpleDateFormat("HH:mm:ss").format(new Date()) + "] Hello " + name + ", request from consumer: " + RpcContext.getContext().getRemoteAddress());
        return "Hello " + name + ", response form provider: " + RpcContext.getContext().getLocalAddress();
	}

}


package com.xiuye.provider;

import org.springframework.context.support.ClassPathXmlApplicationContext;

public class Provider {

    public static void main(String[] args) throws Exception {

        ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/dubbo-demo-provider.xml"});
        context.start();

        System.in.read();
    }

}


package com.xiuye.consumer;

import com.xiuye.service.DemoService;
import org.springframework.context.support.ClassPathXmlApplicationContext;

public class Consumer {

    public static void main(String[] args) {
        ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/dubbo-demo-consumer.xml"});
        context.start();
        DemoService demoService = (DemoService) context.getBean("demoService"); // get remote service proxy

        System.out.println(demoService);

        String hello = demoService.hello("world"); // call remote method
        System.out.println(hello); // get result



    }
}




dubbo-demo-provider.xml

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
       xmlns="http://www.springframework.org/schema/beans"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
       http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">

    <!-- provider's application name, used for tracing dependency relationship -->
    <dubbo:application name="provider"/>

    <!-- use multicast registry center to export service -->
    <dubbo:registry address="multicast://224.0.0.2:1234"/>

    <!-- use dubbo protocol to export service on port 20880 -->
    <dubbo:protocol name="dubbo" port="20880"/>

    <!-- service implementation, as same as regular local bean -->
    <bean id="demoService" class="com.xiuye.provider.DemoServiceImpl"/>

    <!-- declare the service interface to be exported -->
    <dubbo:service interface="com.xiuye.service.DemoService" ref="demoService"/>

</beans>

dubbo.properties

dubbo.application.qos.port=22222

pom.xml


dubbo-demo-consumer.xml

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
       xmlns="http://www.springframework.org/schema/beans"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
       http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">

    <!-- consumer's application name, used for tracing dependency relationship (not a matching criterion),
    don't set it same as provider -->
    <dubbo:application name="consumer"/>

    <!-- use multicast registry center to discover service -->
    <dubbo:registry address="multicast://224.0.0.2:1234"/>

    <!-- generate proxy for the remote service, then demoService can be used in the same way as the
    local regular interface -->
    <dubbo:reference id="demoService" check="true" interface="com.xiuye.service.DemoService"/>


   <!--  <dubbo:protocol host="127.0.0.1"/> -->

</beans>
dubbo.properties 
dubbo.application.qos.port=33333

pom.xml


log4j.properties

###set log levels###
log4j.rootLogger=info, stdout
###output to console###
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d{dd/MM/yy hh:mm:ss:sss z}] %t %5p %c{2}: %m%n

Output:

provider:

[08/03/18 11:07:28:028 CST] main  INFO support.ClassPathXmlApplicationContext: Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@175e721: startup date [Thu Mar 08 23:07:28 CST 2018]; root of context hierarchy
[08/03/18 11:07:29:029 CST] main  INFO xml.XmlBeanDefinitionReader: Loading XML bean definitions from class path resource [META-INF/spring/dubbo-demo-provider.xml]
[08/03/18 11:07:29:029 CST] main  INFO logger.LoggerFactory: using logger: com.alibaba.dubbo.common.logger.log4j.Log4jLoggerAdapter
[08/03/18 11:07:29:029 CST] main  INFO config.AbstractConfig:  [DUBBO] The service ready on spring started. service: com.xiuye.service.DemoService, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:29:029 CST] main  INFO config.AbstractConfig:  [DUBBO] Export dubbo service com.xiuye.service.DemoService to local registry, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:29:029 CST] main  INFO config.AbstractConfig:  [DUBBO] Export dubbo service com.xiuye.service.DemoService to url dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&bind.ip=192.168.56.1&bind.port=20880&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&qos.port=22222&side=provider×tamp=1520521649671, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:29:029 CST] main  INFO config.AbstractConfig:  [DUBBO] Register dubbo service com.xiuye.service.DemoService url dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&bind.ip=192.168.56.1&bind.port=20880&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&qos.port=22222&side=provider×tamp=1520521649671 to registry registry://224.0.0.2:1234/com.alibaba.dubbo.registry.RegistryService?application=provider&dubbo=2.6.1&pid=3724&qos.port=22222&registry=multicast×tamp=1520521649658, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] main  INFO transport.AbstractServer:  [DUBBO] Start NettyServer bind /0.0.0.0:20880, export /192.168.56.1:20880, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Register: dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Send broadcast message: register dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 to /224.0.0.2:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: register dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Subscribe: provider://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&category=configurators&check=false&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Send broadcast message: subscribe provider://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&category=configurators&check=false&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 to /224.0.0.2:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:30:030 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: subscribe provider://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&category=configurators&check=false&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:31:031 CST] main  WARN multicast.MulticastRegistry:  [DUBBO] Ignore empty notify urls for subscribe url provider://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&category=configurators&check=false&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: register consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=consumers&check=false&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: subscribe consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Send broadcast message: register dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 to /224.0.0.2:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: register dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[23:07:41] Hello world, request from consumer: /192.168.56.1:53683
consumer 
[08/03/18 11:07:39:039 CST] main  INFO support.ClassPathXmlApplicationContext: Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@175e721: startup date [Thu Mar 08 23:07:39 CST 2018]; root of context hierarchy
[08/03/18 11:07:39:039 CST] main  INFO xml.XmlBeanDefinitionReader: Loading XML bean definitions from class path resource [META-INF/spring/dubbo-demo-consumer.xml]
[08/03/18 11:07:39:039 CST] main  INFO logger.LoggerFactory: using logger: com.alibaba.dubbo.common.logger.log4j.Log4jLoggerAdapter
[08/03/18 11:07:40:040 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Load registry store file C:\Users\Administrator\.dubbo\dubbo-registry-consumer-224.0.0.2:1234.cache, data: {com.xiuye.service.DemoService=dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=5028&side=provider×tamp=1520520543228}, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Register: consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=consumers&check=false&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Send broadcast message: register consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=consumers&check=false&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 to /224.0.0.2:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: register consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=consumers&check=false&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Subscribe: consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Send broadcast message: subscribe consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 to /224.0.0.2:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: subscribe consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Receive multicast message: register dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671 from /192.168.56.1:1234, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:40:040 CST] DubboMulticastRegistryReceiver  INFO multicast.MulticastRegistry:  [DUBBO] Notify urls for subscribe url consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372, urls: [dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671], dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:41:041 CST] DubboMulticastRegistryReceiver  INFO transport.AbstractClient:  [DUBBO] Successed connect to server /192.168.56.1:20880 from NettyClient 192.168.56.1 using dubbo version 2.6.1, channel is NettyChannel [channel=[id: 0xd843504d, /192.168.56.1:53683 => /192.168.56.1:20880]], dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:41:041 CST] DubboMulticastRegistryReceiver  INFO transport.AbstractClient:  [DUBBO] Start NettyClient xiuye/192.168.56.1 connect to the server /192.168.56.1:20880, dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:41:041 CST] main  INFO multicast.MulticastRegistry:  [DUBBO] Notify urls for subscribe url consumer://192.168.56.1/com.xiuye.service.DemoService?application=consumer&category=providers,configurators,routers&check=true&dubbo=2.6.1&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&side=consumer×tamp=1520521660372, urls: [dubbo://192.168.56.1:20880/com.xiuye.service.DemoService?anyhost=true&application=provider&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3724&side=provider×tamp=1520521649671], dubbo version: 2.6.1, current host: 192.168.56.1
[08/03/18 11:07:41:041 CST] main  INFO config.AbstractConfig:  [DUBBO] Refer dubbo service com.xiuye.service.DemoService from url multicast://224.0.0.2:1234/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=consumer&check=true&dubbo=2.6.1&generic=false&interface=com.xiuye.service.DemoService&methods=hello&pid=3112&qos.port=33333&register.ip=192.168.56.1&remote.timestamp=1520521649671&side=consumer×tamp=1520521660372, dubbo version: 2.6.1, current host: 192.168.56.1
com.alibaba.dubbo.common.bytecode.proxy0@a638b5
Hello world, response form provider: 192.168.56.1:20880



如果maven工程找不到相应的jar包,去Dubbo官网下载源代码---编译.(mvn compile --> mvn package --> mvn install.)

如果eclipse中maven找不到本地刚刚编译jar,"Window" ==> "Show Views" ==> "Other" ==> "Maven Repositories" ==>

"Local Repositories" ==> "Mouse Right Clicked" ==> "Rebuild Index".


参考链接:

Dubbo下载








__BMGT()
关注
专栏目录
Dubbo-SpringBoot::robot: 使用SpringBoot maven构建dubbo demo
05-09
使用SpringBoot maven构建dubbo demo 项目安装 首先安装zookeeper；； 将项目导入eclipse； dubbo-provider服务提供者项目的资源文件 src/main/resources/provides.xml下配置zookeeper地址； dubbo-consumer服务提供...
DubboDemo+spring+maven
08-16
【标题】"DubboDemo+spring+maven"项目是一个基于Dubbo、Spring和Maven的实战示例，旨在展示如何手工搭建并运行一个完整的Dubbo服务提供者（Provider）和消费者（Consumer）系统。 【描述】这个项目的核心是利用...
dubbo-官方demo
weixin_33946020的博客
03-09 463
参考 http://dubbo.apache.org/zh-cn/docs/user/quick-start.html http://dubbo.apache.org/zh-cn/docs/admin/install/provider-demo.html 前提 如果注册中心是zookeeper，需要先安装zookeeper。并且启动zookeeper服务器端。 步骤 配置注册中心地址 运行服务提供...
Dubbo 服务本地缓存
huotongwangbs的专栏
10-15 4722
开篇 根据官方图，dubbo调用者需要通过注册中心（例如：ZK）注册信息，获取提供者，但是如果频繁往ZK获取信息，肯定会存在单点故障问题，所以dubbo提供了将提供者信息缓存在本地的方法。 Dubbo在订阅注册中心的回调处理逻辑当中会保存服务提供者信息到本地缓存文件当中（同步/异步两种方式），以url纬度进行全量保存。 Dubbo在服务引用过程中会创建registry对象并加载本地缓存文件，会优先订阅注册中心，订阅注册中心失败后会访问本地缓存文件内容获取服务提供信息。 核心
对dubbo的DubboReference.check的参数进行剖析
Mmnnnbb123的博客
04-24 980
可以看出：当consumer先启动时，如果provider此时没有启动，consumer就再也访问不到provider的服务了。在使用dubbo的时候，发现当消费者启动的时候，如果提供者没有启动，即使提供者后来启动了，消费者也调不通提供者提供的接口了。可以看出：即使是consumer先启动，当provider启动后，consumer还是能够访问到provider的服务的。字段，那么就会在启动的时候检查提供方是否可用，如果不可用，就销毁了。当没有可用的服务时，instances是空的。
dubbo升级至2.7.15后application配置无法生效
qq_39933337的博客
03-16 3145
dubbo升级至2.7.15之后测试环境交易正常，但是application配置无法生效，如图 配置的端口是28088，但是服务启动之后显示的端口是20880，是dubbo的默认端口，查了相关文档之后才了解到，上面的写法是错误的，2.7.0版本没有校验单复数写法，这种写法在2.7.15版本中不通过，具体校验见 属性配置 | Apache Dubbo知道原因修改写法就可以了，我这边是更换为单数写法： dubbo.protocol.port=28088 之后重启，显示的端口就是28088了； .
[DUBBO] qos-server can not bind localhost:22222端口已占用错误解决
weixin_41224131的博客
04-10 3498
Dubbo启动时出现如下错误 ERROR Server:111 - [DUBBO] qos-server can not bind localhost:22222, dubbo version: 2.7.5, current host: 192.168.2.199 java.net.BindException: Address already in use: bind 是因为dubbo的提供方...
spring dubbo demo
03-26
Spring Dubbo Demo是一个基于Spring和Dubbo框架的简单示例项目，主要用于展示如何在IntelliJ IDEA（简称Idea）开发环境中实现生产者-消费者模式。在这个项目中，我们将探讨Dubbo的核心概念、Spring整合Dubbo的方式...
Maven构建dubbo demo项目
09-05
通过MAVEN构建的DUBBO项目，可在短时间内了解DUBBO的基本使用方法，适合新手入门。在发布示例项目前，需要先下载zookeeper-3.4.10，zookeeper可在WINDOWS下解压后运行bin\zkServer.cmd文件。
dubbo+zookeeper maven demo
11-03
【标题】：“dubbo+zookeeper Maven Demo” 在Java开发领域，Dubbo和Zookeeper是两个极为重要的组件。Dubbo是一款高性能、轻量级的开源Java RPC框架，它提供了服务治理的全套解决方案，包括服务注册与发现、负载...
关于dubbo无法启动QoS服务器：，dubbo版本：2.6.5，当前主机：192.xxx.xxx.xxx。 java.net.BindException: Address already in u...
09-19 2099
启动同构项目时报了"Fail to start qos server"、"qos-server can not bind localhost:22222" 的异常。 查阅dubbo文档后发现，更改方法 解决方案为： 在dubbo.properties 下，添加 dubbo.application.qos.enable=true是否启动QoS dubbo.applic...
[Dubbo] 消费者启动报错 java.net.BindException: Address already in use: bind
最新发布
m0_51935980的博客
03-13 1109
，这意味着Dubbo在尝试绑定QoS服务到本地端口22222时遇到了问题，具体错误原因为。，这表明这个端口已经被其他进程占用，无法被Dubbo QoS服务再次绑定。当Dubbo消费者启动时报错“
ClassNotFoundException: com.alibaba.dubbo.qos.server.DubboLogo 解决方案
明明如月的技术博客
04-25 8846
最近接入dubbo不太顺利，报错如下：ClassNotFoundException: com.alibaba.dubbo.qos.server.DubboLogo最终通请教找到原因，是pom.xml中dubbo依赖有问题，最终pom.xml中配置如下：&lt;!-- Spring Boot Dubbo 依赖--&gt; &lt;dependency&gt; &lt;groupId&gt;...
dubbo异常之应用启动qos-server can not bind localhost:22222
高新富的博客
12-04 7231
https://blog.csdn.net/u012988901/article/details/84503672
Dubbo Failed to bind NettyServer on /192.168.56.1:xx,cause:Address already in use:bind问题解决
旭东怪的博客
10-13 5476
问题描述： Caused by: org.apache.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.56.1:20882, cause: Address already in use: bind 问题分析： 1、当前项目的dubbo端口20882被占用了，导致报错。 dubbo: scan: base-packages: com.basic protocol: ...
Dubbo启动时qos-server can not bind localhost:22222错误解决
hao1454507493的博客
05-06 945
启动生产者,消费者重复了 Qos=Quality of Service，qos是Dubbo的在线运维命令，可以对服务进行动态的配置、控制及查询，Dubboo2.5.8新版本重构了telnet（telnet是从Dubbo2.0.5开始支持的）模块，提供了新的telnet命令支持，新版本的telnet端口与dubbo协议的端口是不同的端口，默认为22222，可以通过配置文件dubbo.propert...
由浅入深写java分布式(4)基于注解 dubbo 一个app同时存在consumer和provider自启动失败的问题，以dubbo和spring注解加载顺序的问题
kkgbn的博客
02-18 9745
问题描述： 将提供者和消费者写再同一个项目，要么提前启动一个纯的提供者app。否则会rpc调用失败。 解决过程： 通过dubbo admin观察要么再linux上只启动成功消费者 要么再windows启动有消费者和生产者，但是调用失败。 一开始分析是@Reference 在spring被dubbo注入的时候没有spring的已经注入结束了，造成NPE。但是这个问题之前用将@Refe
dubbo 分析-调用过程分析
taotoxht的专栏
04-15 910
dubbo 调用过程分析 本章 主要介绍 dubbo 服务和客户端 调用过程。 服务端 接收请求流程 服务端配置 直接采用dubbo 源码例子 dubbo-demo-provider 配置如下： &lt;!-- provider's application name, used for tracing dependency relationship --&gt; &lt;d...
Maven创建与Dubbo集成：金诚接口平台开发指南
本文档主要介绍了如何利用Maven、Zookeeper、Dubbo和Spring MVC技术栈来开发金诚国际接口平台，并详细步骤涵盖了Maven项目的创建、配置和与Dubbo集成的过程。以下是关键知识点的详细解读： 1. **Maven项目创建** -...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值