com.alibaba.dubbo.rpc.RpcException的解决方法

在开发SpringMVC+dubbo框架时，从消费者跳转到提供者时总是报错，报错信息如下：

2016-6-27 15:23:05 org.apache.catalina.core.StandardWrapperValve invoke

严重: Servlet.service() for servlet [spring] in context with path [/mp_consumer] threw exception [Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method login in the service com.MP.manager.JcManager. No provider available for the service com.MP.manager.JcManager from registry 127.0.0.1:2181 on the consumer 192.168.2.215 using the dubbo version 2.5.3. Please check if the providers have been started and registered.] with root cause

com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method login in the service com.MP.manager.JcManager. No provider available for the service com.MP.manager.JcManager from registry 127.0.0.1:2181 on the consumer 192.168.2.215 using the dubbo version 2.5.3. Please check if the providers have been started and registered.

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.checkInvokers(AbstractClusterInvoker.java:246)

    at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:55)

    at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)

    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.login(proxy0.java)

    at com.MP.ctrl.jcCtrl.tologin(jcCtrl.java:62)

    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.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:176)

    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:444)

    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:432)

    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)

    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)

    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:946)

    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:848)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)

    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:822)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)

    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)

    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)

    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)

    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)

    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)

    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:619)

经过反复的查询和调试终于发现是配置的问题,配置文件中id名与控制层声明的接口名称相同即可。

消费者配置：

<dubbo:reference id="jc" interface="com.MP.manager.JcManager" check="false" timeout="12000"/>

jc为控制层中定义的接口名

<pre name="code" class="java">@Scope("prototype")@Controller@RequestMapping("/jc")public class jcCtrl {private JcManager jc;public JcManager getJc() {return jc;}}

提供者配置：

<pre name="code" class="java"> <!-- 声明需要暴露的服务接口 -->    <dubbo:service interface="com.MP.manager.JcManager" ref="jc" />    <!-- 和本地bean一样实现服务 -->    <bean id="jc" class="com.MP.managerImpl.JcManagerImpl" />