dubbo地址冲突

最新推荐文章于 2024-04-14 12:30:26 发布
最新推荐文章于 2024-04-14 12:30:26 发布
阅读量486 收藏
点赞数 2
分类专栏： dubbo
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_39979373/article/details/82873131
版权

Error Message

Failed to load ApplicationContext

Stacktrace

java.lang.IllegalStateException: Failed to load ApplicationContext
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:125)
	at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:108)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:117)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:83)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:246)
	at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.springTestContextPrepareTestInstance(AbstractTestNGSpringContextTests.java:145)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
	at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
	at org.testng.TestRunner.privateRun(TestRunner.java:767)
	at org.testng.TestRunner.run(TestRunner.java:617)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
	at org.testng.TestNG.run(TestNG.java:1031)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:158)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:98)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
	at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
	at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://10.177.12.81:20880/com.netease.logistics.allocate.remote.WarehouseShipmentRemoteApi?anyhost=true&application=logistics-tms-system&channel.readonly.sent=true&codec=dubbo&dubbo=3.0.6&environment=develop&generic=false&heartbeat=60000&indicator=none&interface=com.netease.logistics.allocate.remote.WarehouseShipmentRemoteApi&logger=log4j&methods=warehouseShipment,casecarQuery,billnoQuery,warehouseShipmentForWMS&monitor=dubbo%3A%2F%2F10.165.176.231%3A2181%2Fcom.alibaba.dubbo.registry.RegistryService%3Fapplication%3Dlogistics-tms-system%26backup%3D10.165.176.232%3A2181%2C10.165.176.233%3A2181%26check%3Dfalse%26client%3Dcached%26dubbo%3D3.0.6%26environment%3Ddevelop%26indicator%3Dnone%26logger%3Dlog4j%26organization%3Dhaitao%26owner%3Dzhangxiaochuan%26pid%3D17640%26protocol%3Dregistry%26refer%3Ddubbo%253D3.0.6%2526interface%253Dcom.alibaba.dubbo.monitor.MonitorService%2526pid%253D17640%2526timestamp%253D1538049479609%26register%3Dtrue%26registry%3Dzookeeper%26timestamp%3D1538049479595&organization=haitao&owner=zhangxiaochuan&pid=17640&side=provider&timestamp=1538049479596) Failed to bind NettyServer on /10.177.12.81:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:293)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:270)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:257)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:55)
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:60)
	at com.alibaba.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:38)
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java)
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:165)
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:115)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:58)
	at com.alibaba.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:36)
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:552)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:311)
	at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:267)
	at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:166)
	at com.alibaba.dubbo.config.bootstrap.container.ServiceContainer.export(ServiceContainer.java:41)
	at com.alibaba.dubbo.config.bootstrap.DubboBootstrap.start(DubboBootstrap.java:107)
	at com.alibaba.dubbo.config.spring.bootstrap.listener.DubboStartListener.onApplicationEvent(DubboStartListener.java:18)
	at com.alibaba.dubbo.config.spring.bootstrap.listener.DubboStartListener.onApplicationEvent(DubboStartListener.java:7)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400)
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354)
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:888)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:128)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:107)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:243)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:99)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:117)
	... 39 more
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /10.177.12.81:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:81)
	at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:63)
	at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:33)
	at com.alibaba.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java)
	at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:48)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:41)
	at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:63)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:291)
	... 72 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:303)
	at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:98)
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:76)
	... 79 more
Caused by: java.net.BindException: 地址已在使用
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:148)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:100)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:74)
	at org.jboss.netty.channel.Channels.bind(Channels.java:468)
	at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:192)
	at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:348)
	at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:176)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:85)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:142)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:90)
	at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282)
	... 81 more
Caused by: com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://10.177.12.81:20880/com.netease.logistics.allocate.remote.WarehouseShipmentRemoteApi?anyhost=true&application=logistics-tms-system&channel.readonly.sent=true&codec=dubbo&dubbo=3.0.6&environment=develop&generic=false&heartbeat=60000&indicator=none&interface=com.netease.logistics.allocate.remote.WarehouseShipmentRemoteApi&logger=log4j&methods=warehouseShipment,casecarQuery,billnoQuery,warehouseShipmentForWMS&monitor=dubbo%3A%2F%2F10.165.176.231%3A2181%2Fcom.alibaba.dubbo.registry.RegistryService%3Fapplication%3Dlogistics-tms-system%26backup%3D10.165.176.232%3A2181%2C10.165.176.233%3A2181%26check%3Dfalse%26client%3Dcached%26dubbo%3D3.0.6%26environment%3Ddevelop%26indicator%3Dnone%26logger%3Dlog4j%26organization%3Dhaitao%26owner%3Dzhangxiaochuan%26pid%3D17640%26protocol%3Dregistry%26refer%3Ddubbo%253D3.0.6%2526interface%253Dcom.alibaba.dubbo.monitor.MonitorService%2526pid%253D17640%2526timestamp%253D1538049479609%26register%3Dtrue%26registry%3Dzookeeper%26timestamp%3D1538049479595&organization=haitao&owner=zhangxiaochuan&pid=17640&side=provider&timestamp=1538049479596) Failed to bind NettyServer on /10.177.12.81:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:293)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:270)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:257)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:55)
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:60)
	at com.alibaba.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:38)
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java)
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:165)
	at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:115)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)
	at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:58)
	at com.alibaba.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:36)
	at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:552)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:311)
	at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:267)
	at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:166)
	at com.alibaba.dubbo.config.bootstrap.container.ServiceContainer.export(ServiceContainer.java:41)
	at com.alibaba.dubbo.config.bootstrap.DubboBootstrap.start(DubboBootstrap.java:107)
	at com.alibaba.dubbo.config.spring.bootstrap.listener.DubboStartListener.onApplicationEvent(DubboStartListener.java:18)
	at com.alibaba.dubbo.config.spring.bootstrap.listener.DubboStartListener.onApplicationEvent(DubboStartListener.java:7)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400)
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354)
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:888)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:128)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:107)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:243)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:99)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:117)
	... 39 more
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /10.177.12.81:20880, cause: Failed to bind to: /0.0.0.0:20880
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:81)
	at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:63)
	at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:33)
	at com.alibaba.dubbo.remoting.Transporter$Adaptive.bind(Transporter$Adaptive.java)
	at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:48)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:41)
	at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:63)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:291)
	... 72 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:303)
	at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:98)
	at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:76)
	... 79 more
Caused by: java.net.BindException: 地址已在使用
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:148)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:100)
	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:74)
	at org.jboss.netty.channel.Channels.bind(Channels.java:468)
	at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:192)
	at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:348)
	at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:176)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:85)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:142)
	at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:90)
	at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282)

解决方法：

修改test-essearch-dubbo-provider.xml中dubbo端口（port）

<dubbo:protocol name="dubbo" port="31232" accesslog="true"/>

注意在applicationContext.xml中对test-essearch-dubbo-provider.xml进行配置

<import resource="classpath:test-essearch-dubbo-provider.xml" />

 

加瓦宫程式
关注
  • 2
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
dubbo生态地址
oThrowsException的博客
09-27 161
文章目录alibabaSentineldoubboapollonacos alibaba https://github.com/alibaba Sentinel https://github.com/alibaba/Sentinel/wiki/%E4%BB%8B%E7%BB%8D doubbo https://dubbo.apache.org apollo https://github.com/ctripcorp/apollo nacos https://github.com/alibaba/nacos
解决因多网卡导致dubbo注册到ZK的IP错误问题，dubbox（当当，2.8.4）升级至dubbo（Apache，2.7.15）并集成dubbo-admin
muguazhi的博客
02-19 3579
dubbo.xml配置文件修改1 1.2替换原来dubbo相关标签，改成如下标签（标红位置） <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dubbo="http://dubbo.apache.org/schema/dubbo" xsi:...
Dubbo（从入门到掌握）看完这一篇就够了
最新发布
西敏寺的乐章的博客
04-14 1979
Dubbo是阿里巴巴公司开源的一个高性能、轻量级的 Java RPC 框架。致力于提供高性能和透明化的 RPC 远程服务调用方案，以及 SOA 服务治理方案。
dubbo端口被占用排查记录
weixin_30329623的博客
11-19 1082
## 前提是dubboadmin界面登录不了 1.根据已有应用的端口号，查询占用端口的应用pid： 　　netstat -anp|grep 20891(端口号） 2.使用jps查看启动的java进程列表，确认pid是否是java进程：　　jps -v -> pid 3.确认之后，根据pid查找应用名称： 　　ps -ef|grep pid -> ...
开源一款超实用的 Dubbo 测试工具，已用半年，感觉很有feel~
Java知音
06-17 405
不知道你是否在工作中有遇到过类似情况：dubbo接口调试复杂，需要通过telnet命令或者通过consumer调用来触发。telnet语句参数格式复杂，每次编写都要小心谨慎，一旦出错又需...
dubbo 设置注册到注册中心的IP地址为公网IP
m0_67403076的博客
08-14 1385
报错无法启动 server Cannot assign requested address: bind， 其实是socket无法启动，socket端口外网无法连接， 理由是 如果服务端套接字绑定在它上面，你的客户端程序就只能在本机访问。这里面 暂不讨论源码，总之配置文件中 （dubbo.protocol 或 dubbo.provider 的 host）的host属性，如果要配置 必须配置本机的ip （内网ip 或者 127.0.0.1 或者 不配dubbo自己获取）二是向注册中心注册服务。...
dubbo架构解析文档
11-19
例如，代码冲突频繁，协同开发困难，每次发布涉及大量代码，可能导致系统稳定性下降，技术升级受限等。通过拆分，每个服务的代码量减小，开发人员只需关注自己负责的部分，提高效率，同时允许灵活的技术更新，降低了...
SpringBoot集成dubbo
02-07
1. **版本兼容性**：确保Spring Boot和Dubbo的版本兼容，避免因版本问题引发的冲突。 2. **配置优先级**：理解Spring Boot和Dubbo的配置加载顺序，合理设置配置属性，避免覆盖或遗漏。 3. **异常处理**：对服务调用...
dubbo监控中心管理
08-18
1. **查阅官方文档**：首先，应该参考Dubbo官方文档，了解推荐的依赖组合以及可能存在的冲突。 2. **调整pom.xml**：根据项目需求，修改`pom.xml`文件中的依赖版本，确保与项目其他组件兼容。 3. **排除冲突依赖**...
springboot+dubbo
11-13
2. 配置Dubbo：在`application.properties`或`application.yml`中配置Dubbo的相关属性，如服务端口、协议类型、Zookeeper地址等。 三、服务消费者（Consumer）的配置 1. 创建消费者：消费者通过引用服务提供者的...
dubbo-admin 2.0.0
06-01
默认情况下，Zookeeper的端口是2181，但可以通过配置文件dubbo.properties进行修改，以适应不同的网络环境或避免端口冲突。 在实际部署dubbo-admin时，首先需要下载并安装Zookeeper。例如，这里提供的"zookeeper-...
dubbo注册中心
m0_67393413的博客
04-01 663
Dubbo目前支持4种注册中心,（multicast zookeeper redis simple） 推荐使用Zookeeper注册中心, Multicast注册中心 不需要启动任何中心节点，只要广播地址一样，就可以互相发现 组播受网络结构限制，只适合小规模应用或开发阶段使用。 组播地址段: 224.0.0.0 - 239.255.255.255 相关概念解析： 提供方启动时广播自己的地址。 消费方启动时广播订阅请求。 提供方收到订阅请求时，单播自己的地址给订阅者，如果设置了unicast=false，则
Dubbo基础
@起风了的博客
07-20 424
Dubbo
本地dubbo服务的注册地址不正确问题
juxua_xatu的专栏
03-24 3653
【环境背景】     本机开发了一个dubbo service服务，需要调试。 zookeeper在另一台机器上。 运行调试后，发现本地注册的dubbo服务地址为VMware Network Adapter VMnet8 的地址。 【解决办法】     在配置文件中，增加 dubbo:protocol name="dubbo" port="-1" host="192.168.1.1"
dubbo注册中心服务ip和实际服务提供者ip不一致问题
xysocute的博客
01-07 1008
dubbo注册中心服务ip和实际服务提供者ip不一致问题
四、Dubbo服务启动流程
qq_36364521的博客
12-30 2128
启动类定义 DubboNamespaceHandler解析 dubbo标签具体释义可以查看https://dubbo.apache.org/zh/docsv2.7/user/configuration/xml/ 或 https://dubbo.apache.org/zh/docs/references/xml/ public class DubboNamespaceHandler extends NamespaceHandlerSupport implements ConfigurableSourceBe
Dubbo服务启动异常[Address already in use] 地址被占用
weixin_44644322的博客
04-14 1731
地址参考:https://blog.csdn.net/liusf1993/article/details/90609792 不论我怎么改端口就是会被提示地址被占用,解决办法就是找到conf目录下的server.xml文件 在里面有两个重要的东西 找到 <Host appBase="webapps" autoDeploy="false" deployOnStartup="false" na...
spring context 初始化两次导致dubbo端口被占用
热门推荐
jingyulanye的专栏
05-19 3万+
背景：一个刚开发完的小项目部署到测试环境，总是部署失败，直观的报错是error日志中有dubbo端口被占用。项目为springmvc框架+tomcat。 错误日志为： [0518 19:36:41 354 ERROR] [main] web.context.ContextLoader - Context initialization failed com.alibaba.dubb
dubbo aop 异常失效
09-02
2. AOP切面逻辑与Dubbo拦截器冲突：Dubbo使用拦截器来实现异常处理逻辑，如果AOP切面逻辑与Dubbo拦截器冲突，可能导致AOP异常失效。 3. 异常处理逻辑未生效：Dubbo的AOP功能可以在服务提供者和消费者端进行配置。...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值