阿里巴巴开源服务框架 Dubbo 2.0.10 发布 - 开源软件 - ITeye资讯
阿里巴巴开源服务框架Dubbo2.0.10版本发布了，该版本只修复BUG，没有增加新功能。
Dubbo首页：
Dubbo 2.0.10下载地址：
Dubbo 2.0.10发布记录：
[] - 修复Cluster层传递RpcException的ErrorCode
[] - 增加init属性确定是否在afterpropertiesSet时饥饿初始化
[] - telnet 向上键失效
[] - telnet 缓存问题，历史记录没有设置上限。
[] - bytecode包的Wrapper的反射方法调用，提供方没有重载的方法时，当提供多余的参数时，多余参数会被忽略（应该报错）
[] - 共享连接后，不能使用连接上保存的服务信息，否则多服务时会有问题
[] - DubboCodec在获取函数时没有判断$invoke和$echo等特殊函数
[] - 扩展点加载失败（如依赖的三方库运行时没有），如扩展点没有用到，则加载不要报错（在使用到时报错）
[] - 调用的返回值在Provider端序列化失败（如传输对象没有实现Serialiable接口），Provider端也没有异常输出，Consumer端超时出错
[] - telnet请求没有终结，死循环发送消息
[] - RegistryDirectory在unsubscribe之后再标记为destroyed，否则unsubscribe会失败
[] - zookeeper注册的时候抛ConnectionLoss异常
[] - 配置加载时对${user.home}等占位符没有替换
[] - Config类的toString方法显示的标签名不对
功能改进：
[] - registry客户端缓存采用ip作为key
[] - 服务方法调用重试过程中输出引起重试异常的日志
[] - 通过RpcContext可以获得所有尝试过的Invoker
[] - &dubbo:protocol&未配name时，生成的缺省id也应为dubbo，便于-D参数覆盖
[] - telnet增加--no-prompt参数，用于nc获取信息时不显示提示符
[] - URL基于host自动添加anyhost和localhost参数
[] - 给Multicast和Zookeeper注册中心URL增加缺省端口
ERROR 10:16:41,178 AbstractClient:&init& -& [DUBBO] Failed to start NettyClient caedmon-PC/192.168.0.234 connect to the server /60.191.124.236:21890 (check == false, ignore and retry later!), cause: client(url: dubbo://60.191.124.236:21890/com.sendinfo.ebiz3.account.server.UserServer?anyhost=true&application=wuzhen-b2c-provider&check=false&codec=dubbo&default.check=false&default.retries=0&default.timeout=20000&dubbo=2.5.3&heartbeat=60000&interface=com.sendinfo.ebiz3.account.server.UserServer&methods=queryConsumerPointVo,updateAccount,queryConsumer,updateLogin,loginOut,getLogin,regConsumer,getAccount,queryLogin,updateConsumer&pid=6212&side=consumer&timeout=5000&timestamp=3) failed to connect to server /60.191.124.236:21890 client-side timeout 3000ms (elapsed: 3003ms) from netty client 192.168.0.234 using dubbo version 2.5.3, dubbo version: 2.5.3, current host: 192.168.0.234com.alibaba.dubbo.remoting.RemotingException: client(url: dubbo://60.191.124.236:21890/com.sendinfo.ebiz3.account.server.UserServer?anyhost=true&application=wuzhen-b2c-provider&check=false&codec=dubbo&default.check=false&default.retries=0&default.timeout=20000&dubbo=2.5.3&heartbeat=60000&interface=com.sendinfo.ebiz3.account.server.UserServer&methods=queryConsumerPointVo,updateAccount,queryConsumer,updateLogin,loginOut,getLogin,regConsumer,getAccount,queryLogin,updateConsumer&pid=6212&side=consumer&timeout=5000&timestamp=3) failed to connect to server /60.191.124.236:21890 client-side timeout 3000ms (elapsed: 3003ms) from netty client 192.168.0.234 using dubbo version 2.5.3at com.alibaba.dubbo.remoting.transport.netty.NettyClient.doConnect(NettyClient.java:127)at com.alibaba.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:280)at com.alibaba.dubbo.remoting.transport.AbstractClient.&init&(AbstractClient.java:103)at com.alibaba.dubbo.remoting.transport.netty.NettyClient.&init&(NettyClient.java:61)at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.connect(NettyTransporter.java:37)at com.alibaba.dubbo.remoting.Transporter$Adpative.connect(Transporter$Adpative.java)at com.alibaba.dubbo.remoting.Transporters.connect(Transporters.java:67)at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.connect(HeaderExchanger.java:37)at com.alibaba.dubbo.remoting.exchange.Exchangers.connect(Exchangers.java:102)at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.initClient(DubboProtocol.java:378)at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.getSharedClient(DubboProtocol.java:344)at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.getClients(DubboProtocol.java:321)at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.refer(DubboProtocol.java:303)at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:65)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:62)at com.alibaba.dubbo.rpc.Protocol$Adpative.refer(Protocol$Adpative.java)at com.alibaba.dubbo.registry.integration.RegistryDirectory.toInvokers(RegistryDirectory.java:395)at com.alibaba.dubbo.registry.integration.RegistryDirectory.refreshInvoker(RegistryDirectory.java:224)at com.alibaba.dubbo.registry.integration.RegistryDirectory.notify(RegistryDirectory.java:195)at com.alibaba.dubbo.registry.support.AbstractRegistry.notify(AbstractRegistry.java:449)at com.alibaba.dubbo.registry.support.FailbackRegistry.doNotify(FailbackRegistry.java:273)at com.alibaba.dubbo.registry.support.FailbackRegistry.notify(FailbackRegistry.java:259)at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.access$400(ZookeeperRegistry.java:45)at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry$3.childChanged(ZookeeperRegistry.java:159)at com.alibaba.dubbo.remoting.zookeeper.zkclient.ZkclientZookeeperClient$2.handleChildChange(ZkclientZookeeperClient.java:82)at org.I0Itec.zkclient.ZkClient$8.run(ZkClient.java:583)at org.I0Itec.zkclient.ZkEventThread.run(ZkEventThread.java:71)
先确定一下 redis://172.16.21.177:6379/com.alibaba.dubbo.registry.RegistryService?application=fireballclient&dubbo=2.1.8&interface=com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService&methods=getFireBallInfo&pid=3416&side=consumer&timestamp=2 to the consumer 172.16.53.239 use dubbo version 2.1.8的IP是否是你本机IP，可能是因为找错IP了；如果是这个原因的话将host绑定本机IP就OK
王_辉 写道
redis 127.0.0.1:6379& HGETALL "/dubbo/com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService/providers"
1) "rmi://172.16.21.177:2911/com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService?anyhost=true&application=udep3DubboServer&dubbo=2.1.1&interface=com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService&loadbalance=roundrobin&methods=getFireBallInfo"
Caused by: java.lang.IllegalStateException: Failed to check the status of the service com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService. No provider available for the service com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService from the url redis://172.16.21.177:6379/com.alibaba.dubbo.registry.RegistryService?application=fireballclient&dubbo=2.1.8&interface=com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService&methods=getFireBallInfo&pid=3416&side=consumer&timestamp=2 to the consumer 172.16.53.239 use dubbo version 2.1.8
at com.alibaba.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:359)
at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:252)
at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:107)
at com.alibaba.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:52)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:121)
从redis里边看到服务已经注册，但是客户端调用的失败，是不是和dubbo的版本有关系呢？请问这个问题解决了吗？
redis 127.0.0.1:6379& HGETALL "/dubbo/com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService/providers"
1) "rmi://172.16.21.177:2911/com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService?anyhost=true&application=udep3DubboServer&dubbo=2.1.1&interface=com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService&loadbalance=roundrobin&methods=getFireBallInfo"
Caused by: java.lang.IllegalStateException: Failed to check the status of the service com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService. No provider available for the service com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService from the url redis://172.16.21.177:6379/com.alibaba.dubbo.registry.RegistryService?application=fireballclient&dubbo=2.1.8&interface=com.hundsun.gildata.udep.module.main.service.sysmanage.interfaces.IUserExternalService&methods=getFireBallInfo&pid=3416&side=consumer&timestamp=2 to the consumer 172.16.53.239 use dubbo version 2.1.8
at com.alibaba.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:359)
at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:252)
at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:107)
at com.alibaba.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:52)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:121)
从redis里边看到服务已经注册，但是客户端调用的失败，是不是和dubbo的版本有关系呢？
javatar 写道王_辉 写道亲：dubbo:service配置了token="true"客户端dubbo:reference配置或者怎么样连接服务呢，“在注册中心控制权限，以决定要不要下发令牌给消费者”这句何解？在内部的注册中心上会有一个授权模块，负责服务权限的管理，然后由注册中心基于服务权限决定是否推送token信息给消费方，开源的注册中心暂不支持。那是否有替代方案，或者什么时候在redis或者kp上支持呢
王_辉 写道亲：dubbo:service配置了token="true"客户端dubbo:reference配置或者怎么样连接服务呢，“在注册中心控制权限，以决定要不要下发令牌给消费者”这句何解？在内部的注册中心上会有一个授权模块，负责服务权限的管理，然后由注册中心基于服务权限决定是否推送token信息给消费方，开源的注册中心暂不支持。
亲：dubbo:service配置了token="true"客户端dubbo:reference配置或者怎么样连接服务呢，“在注册中心控制权限，以决定要不要下发令牌给消费者”这句何解？
王_辉 写道redis注册中心，windows正常，服务放到linux可以注册成功，客户端调用的时候就会抛异常
No provider available for the service com.fireball.service.BaseDataService from 亲& 着急啊，给点思路找不到服务提供方，你确定提供者已注册到redis上？有没有用redis命令行查看一下数据？
redis注册中心，windows正常，服务放到linux可以注册成功，客户端调用的时候就会抛异常
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'basedataservice': FactoryBean threw exceptio nested exception is java.lang.IllegalStateException: Failed to check the status of the service com.fireball.service.BaseDataService. No provider available for the service com.fireball.service.BaseDataService from the url redis://172.16.53.239:6379/com.alibaba.dubbo.registry.RegistryService?application=fireballclient&cluster=failsafe&dubbo=2.1.2&interface=com.fireball.service.BaseDataService&loadbalance=roundrobin&methods=test,query&pid=4696&retries=0&timestamp=0 to the consumer 172.16.53.239 use dubbo version 2.1.2
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
at com.fireball.SpringContext.getHsqlDBService(SpringContext.java:57)
at com.fireball.TestMain.&clinit&(TestMain.java:19)
Caused by: java.lang.IllegalStateException: Failed to check the status of the service com.fireball.service.BaseDataService. No provider available for the service com.fireball.service.BaseDataService from the url redis://172.16.53.239:6379/com.alibaba.dubbo.registry.RegistryService?application=fireballclient&cluster=failsafe&dubbo=2.1.2&interface=com.fireball.service.BaseDataService&loadbalance=roundrobin&methods=test,query&pid=4696&retries=0&timestamp=0 to the consumer 172.16.53.239 use dubbo version 2.1.2
at com.alibaba.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:357)
at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:250)
at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:107)
at com.alibaba.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:52)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:121)
... 10 more亲& 着急啊，给点思路
王_辉 写道...有问题，建议你发邮件到Dubbo的邮件组，在这里不一定会及时回复。邮件组地址：
王_辉 写道服务端会抛异常，能帮我看看什么原因No provider available for the service com.alibaba.dubbo.monitor.MonitorService这是因为没有启动监控中心，却配了监控地址，把监控中心启动，或者把xml配置中的&dubbo:monitor protocol="registry"&或properties配置中的dubbo.monitor.protocol=registry去掉。
javatar 写道王_辉 写道linux部署dubbo-demo-provider，dubbo.protocol.name=dubbo配置是没问题的，但是改成rmi就会抛异常java.net.ConnectException: Connection refused: connect连接拒绝，可以用telnet 172.16.22.82 20880测一下，可能是服务提供者没启动，或者防火墙阻挡。linux的hostname是127.0.0.1改了host就好了。服务端会抛异常，能帮我看看什么原因
com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method count in the service com.alibaba.dubbo.monitor.MonitorService. No provider available for the service com.alibaba.dubbo.monitor.MonitorService from registry 172.16.53.172:2186 on the consumer 172.16.22.82 using the dubbo version 2.1.2. Please check if the providers have been started and registered.
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.checkInvokers(AbstractClusterInvoker.java:245)
at com.alibaba.dubbo.rpc.cluster.support.FailsafeClusterInvoker.doInvoke(FailsafeClusterInvoker.java:46)
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:226)
at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)
at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)
at com.alibaba.dubbo.common.bytecode.proxy2.count(proxy2.java)
at com.alibaba.dubbo.monitor.dubbo.DubboMonitor.send(DubboMonitor.java:112)
at com.alibaba.dubbo.monitor.dubbo.DubboMonitor$1.run(DubboMonitor.java:69)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
王_辉 写道linux部署dubbo-demo-provider，dubbo.protocol.name=dubbo配置是没问题的，但是改成rmi就会抛异常java.net.ConnectException: Connection refused: connect连接拒绝，可以用telnet 172.16.22.82 20880测一下，可能是服务提供者没启动，或者防火墙阻挡。
linux部署dubbo-demo-provider，dubbo.protocol.name=dubbo配置是没问题的，但是改成rmi就会抛异常
com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method sayHello in the service com.fireball.service.DemoService. Tried 3 times of the providers [172.16.22.82:20880] (1/1) from the registry 172.16.22.82:2181 on the consumer 172.16.53.239 using the dubbo version 2.1.2. Last error is: Failed to invoke remote service: interface com.fireball.service.DemoService, method: sayHello, url: rmi://172.16.22.82:20880/com.fireball.service.DemoService?anyhost=true&application=fireballclient&check=false&dubbo=2.1.2&interface=com.fireball.service.DemoService&loadbalance=roundrobin&methods=sayHello&pid=4840&revision=test&timestamp=2, cause: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused: connect
at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:91)
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:226)
at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)
at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)
at com.alibaba.dubbo.common.bytecode.proxy0.sayHello(proxy0.java)
at com.TEst.main(TEst.java:20)
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
at org.springframework.remoting.rmi.RmiInvocationWrapper_Stub.invoke(Unknown Source)
at org.springframework.remoting.rmi.RmiClientInterceptor.doInvoke(RmiClientInterceptor.java:397)
at org.springframework.remoting.rmi.RmiClientInterceptor.doInvoke(RmiClientInterceptor.java:343)
at org.springframework.remoting.rmi.RmiClientInterceptor.refreshAndRetry(RmiClientInterceptor.java:329)
at org.springframework.remoting.rmi.RmiClientInterceptor.handleRemoteConnectFailure(RmiClientInterceptor.java:305)
at org.springframework.remoting.rmi.RmiClientInterceptor.invoke(RmiClientInterceptor.java:261)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy7.sayHello(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.alibaba.dubbo.rpc.protocol.rmi.RmiProtocol$2.invoke(RmiProtocol.java:211)
at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)
at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:73)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:50)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:47)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)
at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:67)
... 5 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.&init&(Socket.java:375)
at java.net.Socket.&init&(Socket.java:189)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
... 31 more
13:12:36,828 [myid:] - WARN& [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:286:NIOServerCnxn@349] - caught end of stream exceptionEndOfStreamException: Unable to read additional data from client sessionid 0x0,likely client has closed socket&&&&&&& at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:22)&&&&&&& at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFatory.java:224)&&&&&&& at java.lang.Thread.run(Unknown Source)linux连接zookeeper提示
王_辉 写道2.1.2是不是把http协议去掉了？com.alibaba.dubbo.rpc.http.ServiceDispatcherServlet在jar里边也没有HTTP协议还没有加到开源版本中，因为实现的不通用，只是针对公司内部场景实现的，正在调整，会在5月份的2.3.0版本发布。
2.1.2是不是把http协议去掉了？com.alibaba.dubbo.rpc.http.ServiceDispatcherServlet在jar里边也没有
王_辉 写道现在遇到一个问题，不知道dubbo支不支持服务器端推送消息到各客户端？或者可以推荐目前成熟的java应用参见：
现在遇到一个问题，不知道dubbo支不支持服务器端推送消息到各客户端？或者可以推荐目前成熟的java应用
& 上一页 1
相关资源推荐