dubbo no provider available for the service

小斯AN 2015-07-14 03:24:06
java.lang.IllegalStateException: Failed to check the status of the service com.haier.mobilemall.service.user.IUserService. No provider available for the service com.haier.mobilemall.service.user.IUserService from the url zookeeper://192.168.1.17:2181/com.alibaba.dubbo.registry.RegistryService?application=myHaier-web&dubbo=2.5.3&interface=com.haier.mobilemall.service.user.IUserService&methods=getUserByUserName,getUserByTelphone&pid=8784&revision=0.0.1-SNAPSHOT&side=consumer&timeout=30000×tamp=1436855500866 to the consumer 192.168.253.1 use dubbo version 2.5.3
at com.alibaba.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:420)
at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300)
at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:138)
at com.alibaba.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:65)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1523)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:251)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireByName(AbstractAutowireCapableBeanFactory.java:1240)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1190)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:664)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:630)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:678)
at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:549)
at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:490)
at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:136)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:444)
at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:272)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:770)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:250)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1179)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:598)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:496)
at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:175)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:164)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:93)
at org.eclipse.jetty.server.Server.doStart(Server.java:244)
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:67)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:447)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:387)
at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:555)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
2015-07-14 14:31:50.449:INFO::Started SelectChannelConnector@0.0.0.0:8080
[INFO] Started Jetty Server
...全文
34928 11 打赏 收藏 转发到动态 举报
写回复
用AI写文章
11 条回复
切换为时间正序
请发表友善的回复…
发表回复
lin_guangling 2017-10-28
  • 打赏
  • 举报
回复
http://blog.csdn.net/lin_guangling/article/details/78373247
sinat_35938012 2017-08-22
  • 打赏
  • 举报
回复
我的解决办法:http://www.bubuko.com/infodetail-2250226.html
水上冰石 2017-04-19
  • 打赏
  • 举报
回复
引用 8 楼 jiao_zg 的回复:
[quote=引用 6 楼 jiao_zg 的回复:] 我也遇到这个问题,我的是springmvc+dubbo。web的module依赖了api层,api层依赖了service层的接口,没有依赖serviceImpl。然后启动dubbo容器,service不被启动,找不到provider
我的找到问题了,是serviceImpl启动dubbo的provider没成功。解决: 用这个结构,然后运行App那个类。就可以启动了。到tomcat下的dubbo.war中就可以看得到。[/quote] 代码:

/**
 * 启动dubbo容器!
 * 
 */
public class App {
	public static void main(String[] args) throws Exception {

		ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(
				new String[] { "global-fairy-dubbo-provider.xml" });

		context.start();

		System.out.println("Press any key to exit.");

		System.in.read();

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

<beans xmlns="http://www.springframework.org/schema/beans"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p"
	xmlns:context="http://www.springframework.org/schema/context"
	xmlns:mvc="http://www.springframework.org/schema/mvc"
	xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.1.xsd   
       http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.1.xsd   
       http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.1.xsd   
       http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.1.xsd
       http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">
     
	<dubbo:application name ="global-fairy-dubbo-product-provider"/>
	
	<!-- 注册中心 -->
	<dubbo:registry  address="zookeeper://127.0.0.1:2181"/>

	<!-- 默认支持的协议 -->
	<dubbo:protocol name="dubbo" port="20880"/>
	
	<dubbo:service interface="org.global.fairy.service.IUserService" ref = "userService"/>
	
	<bean id = "userService" class = "org.global.fairy.service.impl.UserServiceImpl"/>
</beans>
水上冰石 2017-04-19
  • 打赏
  • 举报
回复
引用 6 楼 jiao_zg 的回复:
我也遇到这个问题,我的是springmvc+dubbo。web的module依赖了api层,api层依赖了service层的接口,没有依赖serviceImpl。然后启动dubbo容器,service不被启动,找不到provider


我的找到问题了,是serviceImpl启动dubbo的provider没成功。解决:

用这个结构,然后运行App那个类。就可以启动了。到tomcat下的dubbo.war中就可以看得到。
FloodWater1989 2017-04-18
  • 打赏
  • 举报
回复
请问您怎么解决的这个问题
水上冰石 2017-04-11
  • 打赏
  • 举报
回复
我也遇到这个问题,我的是springmvc+dubbo。web的module依赖了api层,api层依赖了service层的接口,没有依赖serviceImpl。然后启动dubbo容器,service不被启动,找不到provider
我说假如 2015-12-03
  • 打赏
  • 举报
回复
lz有解决吗?我也遇到了,有点不稳定
java代码民工 2015-11-13
  • 打赏
  • 举报
回复
UserService没有注入到你的服务端
星际飘渺 2015-11-02
  • 打赏
  • 举报
回复
这个问题如何解决??
小斯AN 2015-07-15
  • 打赏
  • 举报
回复
2181 这个端口的服务起来了呀
  • 打赏
  • 举报
回复
dubbo服务没有提供者,你看看2181 这个端口的服务起来了没有

67,513

社区成员

发帖
与我相关
我的任务
社区描述
J2EE只是Java企业应用。我们需要一个跨J2SE/WEB/EJB的微容器,保护我们的业务核心组件(中间件),以延续它的生命力,而不是依赖J2SE/J2EE版本。
社区管理员
  • Java EE
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧