本文旨在搭建dubbo 基础演示示例，并使用dubbo Admin进行管理。
一、dubbo-admin:
下载地址：https://github.com/apache/incubator-dubbo-ops
执行命令：
cd incubator-dubbo-ops && mvn package
打包成功：
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ dubbo-registry-simple ---
[INFO] Building jar: D:codeincubator-dubbo-ops-masterdubbo-registry-simple argetdubbo-registry-simple-2.0.0.jar
[INFO]
[INFO] --- maven-dependency-plugin:2.10:unpack (unpack) @ dubbo-registry-simple ---
[INFO] Configured Artifact: com.alibaba:dubbo:2.6.0:jar
[INFO] Unpacking C:Users
oot.m2
epositorycomalibabadubbo2.6.0dubbo-2.6.0.jar to D:codeincubator-dubbo-ops-masterdubbo-registry-simple argetdubbo with includes "META-INF/assembly/**" and excludes ""
[INFO]
[INFO] --- maven-assembly-plugin:2.6:single (make-assembly) @ dubbo-registry-simple ---
[INFO] Building tar: D:codeincubator-dubbo-ops-masterdubbo-registry-simple argetdubbo-registry-simple-2.0.0-assembly.tar.gz
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] dubbo-ops .......................................... SUCCESS [ 0.008 s]
[INFO] dubbo-admin ........................................ SUCCESS [03:27 min]
[INFO] dubbo-monitor-simple ............................... SUCCESS [01:33 min]
[INFO] dubbo-registry-simple .............................. SUCCESS [ 3.709 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:07 min
[INFO] Finished at: 2018-05-31T13:31:48+08:00
[INFO] Final Memory: 21M/251M
[INFO] ------------------------------------------------------------------------
得到WAR包，放置到Tomcat工程中。
http://localhost:8080/dubbo-admin-2.0.0/ 用户名密码都是root
二、zookeeper:
下载地址：http://mirror.bit.edu.cn/apache/zookeeper/zookeeper-3.4.12/
新建zoo.cfg文件，内容如下：
# The number of milliseconds of each tick tickTime=2000 # The number of ticks that the initial # synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit=5 # the directory where the snapshot is stored. # do not use /tmp for storage, /tmp here is just # example sakes. dataDir=D:soft\zookeeper-3.4.12\ # the port at which the clients will connect clientPort=2181 # the maximum number of client connections. # increase this if you need to handle more clients #maxClientCnxns=60 # # Be sure to read the maintenance section of the # administrator guide before turning on autopurge. # # http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance # # The number of snapshots to retain in dataDir #autopurge.snapRetainCount=3 # Purge task interval in hours # Set to "0" to disable auto purge feature #autopurge.purgeInterval=1
在conf目录下，新增data目录，并创建myid文件，内容为1
启动zookeeper
zkServer.cmd
查看启动情况：
PS D:softzookeeper-3.4.12in> jps -l -v 14388 org.apache.catalina.startup.Bootstrap -Djava.util.logging.config.file=D:softapache-tomcat-9.0.8conflogging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms256M -Xmx512M -XX:PermSize=256M -XX:MaxPermSize=512M -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dignore.endorsed.dirs= -Dcatalina.base=D:softapache-tomcat-9.0.8 -Dcatalina.home=D:softapache-tomcat-9.0.8 -Djava.io.tmpdir=D:softapache-tomcat-9.0.8 emp 17428 org.apache.zookeeper.server.quorum.QuorumPeerMain -Dzookeeper.log.dir=D:softzookeeper-3.4.12in.. -Dzookeeper.root.logger=INFO,CONSOLE 12328 sun.tools.jps.Jps -Denv.class.path=.;C:Program FilesJavajdk1.8.0_121libdt.jar;C:Program FilesJavajdk1.8.0_121lib ools.jar; -Dapplication.home=C:Program FilesJavajdk1.8.0_121 -Xms8m PS D:softzookeeper-3.4.12in> .zkCli.cmd 127.0.0.1:2181 Connecting to localhost:2181 [myid:] - INFO [main:Environment@100] - Client environment:zookeeper.version=3.4.12-e5259e437540f349646870ea94dc2658c4e44b3b, built on 03/27/2018 03:55 GMT [myid:] - INFO [main:Environment@100] - Client environment:host.name=DESKTOP-FL8DUN9 [myid:] - INFO [main:Environment@100] - Client environment:java.version=1.8.0_121 [myid:] - INFO [main:Environment@100] - Client environment:java.vendor=Oracle Corporation [myid:] - INFO [main:Environment@100] - Client environment:java.home=C:Program FilesJavajdk1.8.0_121jre [myid:] - INFO [main:Environment@100] - Client environment:java.class.path=D:softzookeeper-3.4.12in..uildclasses;D:softzookeeper-3.4.12in..uildlib*;D:softzookeeper-3.4.12in..zookeeper-3.4.12.jar;D:softzookeeper-3.4.12in..libaudience-annotations-0.5.0.jar;D:softzookeeper-3.4.12in..libjline-0.9.94.jar;D:softzookeeper-3.4.12in..liblog4j-1.2.17.jar;D:softzookeeper-3.4.12in..lib etty-3.10.6.Final.jar;D:softzookeeper-3.4.12in..libslf4j-api-1.7.25.jar;D:softzookeeper-3.4.12in..libslf4j-log4j12-1.7.25.jar;D:softzookeeper-3.4.12in..conf [myid:] - INFO [main:Environment@100] - Client environment:java.library.path=C:Program FilesJavajdk1.8.0_121in;C:WINDOWSSunJavain;C:WINDOWSsystem32;C:WINDOWS;C:ProgramDataOracleJavajavapath;C:Program FilesVanDyke SoftwareClients;C:Program Files (x86)InteliCLS Client;C:Program FilesInteliCLS Client;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:WINDOWSSystem32WindowsPowerShellv1.0;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsDAL;C:Program FilesIntelIntel(R) Management Engine ComponentsDAL;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsIPT;C:Program FilesIntelIntel(R) Management Engine ComponentsIPT;D:softapache-maven-3.3.9in;C:Program FilesJavajdk1.8.0_121in;C:Program FilesJavajdk1.8.0_121jrein;C:Program FilesIntelWiFiin;C:Program FilesCommon FilesIntelWirelessCommon;C:WINDOWSSystem32OpenSSH;C:Users ootAppDataLocalMicrosoftWindowsApps;;.
查看dubbo界面，zookeeper已经正常启动
三、配置Provider和Consumer服务
1.provider
修改dubbo-demo-provider.xml
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dubbo="http://dubbo.apache.org/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-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd"> <!-- provider's application name, used for tracing dependency relationship --> <dubbo:application name="demo-provider"/> <!-- use multicast registry center to export service --> <!--dubbo:registry address="multicast://224.5.6.7:1234"/ --> <dubbo:registry address="zookeeper://localhost:2181"/> <!-- use dubbo protocol to export service on port 20880 --> <dubbo:protocol name="dubbo" port="20881"/> <!-- service implementation, as same as regular local bean --> <bean id="demoService" class="com.alibaba.dubbo.demo.provider.DemoServiceImpl"/> <!-- declare the service interface to be exported --> <dubbo:service interface="com.alibaba.dubbo.demo.DemoService" ref="demoService"/> </beans>
直接run application
2. Consumer
修改dubbo-demo-consumer.xml
<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dubbo="http://dubbo.apache.org/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-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/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="demo-consumer"/> <!-- use multicast registry center to discover service --> <dubbo:registry address="zookeeper://localhost:2181"/> <!-- 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="false" interface="com.alibaba.dubbo.demo.DemoService"/> </beans>
同样的方法，启动consumer.
main INFO zookeeper.ZookeeperRegistry: [DUBBO] Subscribe: consumer://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=providers,configurators,routers&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO zookeeper.ZookeeperRegistry: [DUBBO] Notify urls for subscribe url consumer://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=providers,configurators,routers&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394, urls: [dubbo://169.254.115.251:20880/com.alibaba.dubbo.demo.DemoService?anyhost=true&application=demo-provider&dubbo=2.6.2-SNAPSHOT&generic=false&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=19864&side=provider×tamp=1527754536385, dubbo://169.254.115.251:20881/com.alibaba.dubbo.demo.DemoService?anyhost=true&application=demo-provider&dubbo=2.6.2-SNAPSHOT&generic=false&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=20060&side=provider×tamp=1527755394676, empty://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=configurators&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394, empty://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=routers&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO transport.AbstractClient: [DUBBO] Successed connect to server /169.254.115.251:20880 from NettyClient 169.254.115.251 using dubbo version 2.6.2-SNAPSHOT, channel is NettyChannel [channel=[id: 0x56d1d547, /169.254.115.251:64543 => /169.254.115.251:20880]], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO transport.AbstractClient: [DUBBO] Start NettyClient DESKTOP-FL8DUN9/169.254.115.251 connect to the server /169.254.115.251:20880, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO transport.AbstractClient: [DUBBO] Successed connect to server /169.254.115.251:20881 from NettyClient 169.254.115.251 using dubbo version 2.6.2-SNAPSHOT, channel is NettyChannel [channel=[id: 0x677eab21, /169.254.115.251:64544 => /169.254.115.251:20881]], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO transport.AbstractClient: [DUBBO] Start NettyClient DESKTOP-FL8DUN9/169.254.115.251 connect to the server /169.254.115.251:20881, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 main INFO config.AbstractConfig: [DUBBO] Refer dubbo service com.alibaba.dubbo.demo.DemoService from url zookeeper://localhost:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=demo-consumer&check=false&dubbo=2.6.2-SNAPSHOT&generic=false&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333®ister.ip=169.254.115.251&remote.timestamp=1527754536385&side=consumer×tamp=1527755444394, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20880
Hello world, response from provider: 169.254.115.251:20881
Hello world, response from provider: 169.254.115.251:20881
Hello world, response from provider: 169.254.115.251:20880
四、Admin基础操作
禁用服务：20880
[31/05/18 04:37:44:044 CST] main-EventThread INFO zookeeper.ZookeeperRegistry: [DUBBO] Notify urls for subscribe url consumer://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=providers,configurators,routers&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394, urls: [override://169.254.115.251:20880/com.alibaba.dubbo.demo.DemoService?category=configurators&disabled=true&dynamic=false&enabled=true, override://169.254.115.251:20880/com.alibaba.dubbo.demo.DemoService?category=configurators&dynamic=false&enabled=true&weight=50], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 [31/05/18 04:37:44:044 CST] main-EventThread INFO netty.NettyChannel: [DUBBO] Close netty channel [id: 0x1ddf4070, /169.254.115.251:64661 => /169.254.115.251:20880], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 [31/05/18 04:37:44:044 CST] DubboSharedHandler-thread-2 INFO dubbo.DubboProtocol: [DUBBO] disconnected from /169.254.115.251:20880,url:dubbo://169.254.115.251:20880/com.alibaba.dubbo.demo.DemoService?anyhost=true&application=demo-consumer&check=false&codec=dubbo&dubbo=2.6.2-SNAPSHOT&generic=false&heartbeat=60000&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333®ister.ip=169.254.115.251&remote.timestamp=1527754536385&side=consumer×tamp=1527755444394&weight=50, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20881
启动服务：20880
[31/05/18 04:35:47:047 CST] main-EventThread INFO zookeeper.ZookeeperRegistry: [DUBBO] Notify urls for subscribe url consumer://169.254.115.251/com.alibaba.dubbo.demo.DemoService?application=demo-consumer&category=providers,configurators,routers&check=false&dubbo=2.6.2-SNAPSHOT&interface=com.alibaba.dubbo.demo.DemoService&methods=sayHello&pid=18152&qos.port=33333&side=consumer×tamp=1527755444394, urls: [override://169.254.115.251:20880/com.alibaba.dubbo.demo.DemoService?category=configurators&dynamic=false&enabled=true&weight=50], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 [31/05/18 04:35:47:047 CST] main-EventThread INFO transport.AbstractClient: [DUBBO] Successed connect to server /169.254.115.251:20880 from NettyClient 169.254.115.251 using dubbo version 2.6.2-SNAPSHOT, channel is NettyChannel [channel=[id: 0x1ddf4070, /169.254.115.251:64661 => /169.254.115.251:20880]], dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 [31/05/18 04:35:47:047 CST] main-EventThread INFO transport.AbstractClient: [DUBBO] Start NettyClient DESKTOP-FL8DUN9/169.254.115.251 connect to the server /169.254.115.251:20880, dubbo version: 2.6.2-SNAPSHOT, current host: 169.254.115.251 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20880 Hello world, response from provider: 169.254.115.251:20881 Hello world, response from provider: 169.254.115.251:20880
五、可能遇到的问题：
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /169.254.115.251:20880, cause: Failed to bind to: /0.0.0.0:20880 at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:69) at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:61) at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:32) at com.alibaba.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java) at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:56) at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:44) at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:70) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:285) ... 26 more Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /0.0.0.0:20880 at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272) at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:94) at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:63) ... 33 more Caused by: java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315) at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
<!-- use dubbo protocol to export service on port 20880 --> <dubbo:protocol name="dubbo" port="20881"/>
六、参考链接：
1. 管理控制台运维：http://dubbo.apache.org/books/dubbo-admin-book/ops/dubbo-ops.html
2. https://github.com/nomico271/DatatablesDemo
七、附录
Dubbo整个工程：
[INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] dubbo-parent ....................................... SUCCESS [ 4.811 s] [INFO] Hessian Lite(Alibaba embed version) ................ SUCCESS [ 8.586 s] [INFO] dubbo-common ....................................... SUCCESS [ 11.352 s] [INFO] dubbo-container .................................... SUCCESS [ 0.146 s] [INFO] dubbo-container-api ................................ SUCCESS [ 1.299 s] [INFO] dubbo-container-spring ............................. SUCCESS [ 33.207 s] [INFO] dubbo-container-log4j .............................. SUCCESS [ 2.283 s] [INFO] dubbo-container-logback ............................ SUCCESS [ 13.599 s] [INFO] dubbo-serialization ................................ SUCCESS [ 0.193 s] [INFO] dubbo-serialization-api ............................ SUCCESS [ 2.761 s] [INFO] dubbo-serialization-hessian2 ....................... SUCCESS [ 3.632 s] [INFO] dubbo-remoting ..................................... SUCCESS [ 0.135 s] [INFO] dubbo-remoting-api ................................. SUCCESS [ 5.654 s] [INFO] dubbo-remoting-netty ............................... SUCCESS [ 3.003 s] [INFO] dubbo-remoting-mina ................................ SUCCESS [ 9.026 s] [INFO] dubbo-remoting-grizzly ............................. SUCCESS [ 22.080 s] [INFO] dubbo-remoting-p2p ................................. SUCCESS [ 2.649 s] [INFO] dubbo-remoting-http ................................ SUCCESS [01:10 min] [INFO] dubbo-remoting-zookeeper ........................... SUCCESS [ 47.235 s] [INFO] dubbo-remoting-netty4 .............................. SUCCESS [ 27.243 s] [INFO] dubbo-rpc .......................................... SUCCESS [ 0.415 s] [INFO] dubbo-rpc-api ...................................... SUCCESS [ 4.839 s] [INFO] dubbo-rpc-dubbo .................................... SUCCESS [ 4.062 s] [INFO] dubbo-rpc-injvm .................................... SUCCESS [ 2.573 s] [INFO] dubbo-rpc-rmi ...................................... SUCCESS [ 2.481 s] [INFO] dubbo-rpc-hessian .................................. SUCCESS [ 12.637 s] [INFO] dubbo-rpc-http ..................................... SUCCESS [ 14.609 s] [INFO] dubbo-rpc-webservice ............................... SUCCESS [ 47.648 s] [INFO] dubbo-cluster ...................................... SUCCESS [ 4.687 s] [INFO] dubbo-registry ..................................... SUCCESS [ 0.115 s] [INFO] dubbo-registry-api ................................. SUCCESS [ 3.163 s] [INFO] dubbo-monitor ...................................... SUCCESS [ 0.090 s] [INFO] dubbo-monitor-api .................................. SUCCESS [ 2.316 s] [INFO] dubbo-filter ....................................... SUCCESS [ 0.092 s] [INFO] dubbo-filter-validation ............................ SUCCESS [ 4.707 s] [INFO] dubbo-filter-cache ................................. SUCCESS [02:53 min] [INFO] dubbo-registry-default ............................. SUCCESS [ 4.062 s] [INFO] dubbo-monitor-default .............................. SUCCESS [ 3.153 s] [INFO] dubbo-registry-multicast ........................... SUCCESS [ 3.263 s] [INFO] dubbo-serialization-jdk ............................ SUCCESS [ 3.538 s] [INFO] dubbo-config ....................................... SUCCESS [ 0.116 s] [INFO] dubbo-config-api ................................... SUCCESS [ 24.591 s] [INFO] dubbo-bootstrap .................................... SUCCESS [ 1.403 s] [INFO] dubbo-config-spring ................................ SUCCESS [ 19.871 s] [INFO] dubbo-rpc-thrift ................................... SUCCESS [ 15.072 s] [INFO] dubbo-rpc-memcached ................................ SUCCESS [ 10.928 s] [INFO] dubbo-rpc-redis .................................... SUCCESS [ 13.896 s] [INFO] dubbo-rpc-rest ..................................... SUCCESS [ 38.378 s] [INFO] dubbo-registry-zookeeper ........................... SUCCESS [ 2.759 s] [INFO] dubbo-registry-redis ............................... SUCCESS [ 50.612 s] [INFO] dubbo-demo ......................................... SUCCESS [ 0.081 s] [INFO] dubbo-demo-api ..................................... SUCCESS [ 0.898 s] [INFO] dubbo-demo-provider ................................ SUCCESS [ 1.367 s] [INFO] dubbo-demo-consumer ................................ SUCCESS [ 1.448 s] [INFO] dubbo-plugin ....................................... SUCCESS [ 0.097 s] [INFO] dubbo-qos .......................................... SUCCESS [ 10.754 s] [INFO] dubbo-serialization-fastjson ....................... SUCCESS [ 2.624 s] [INFO] dubbo-serialization-kryo ........................... SUCCESS [ 3.611 s] [INFO] dubbo-serialization-fst ............................ SUCCESS [ 3.787 s] [INFO] dubbo-dependencies-bom ............................. SUCCESS [ 0.062 s] [INFO] dubbo-bom .......................................... SUCCESS [ 0.018 s] [INFO] dubbo-all .......................................... SUCCESS [09:06 min] [INFO] dubbo-test ......................................... SUCCESS [ 0.552 s] [INFO] dubbo-test-benchmark ............................... SUCCESS [01:03 min] [INFO] dubbo-test-compatibility ........................... SUCCESS [ 0.451 s] [INFO] dubbo-test-spring3 ................................. SUCCESS [ 25.034 s] [INFO] dubbo-test-integration ............................. SUCCESS [ 0.302 s] [INFO] dubbo-test-examples ................................ SUCCESS [ 6.596 s]