com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method selAllStar in the service com.bjsxt.

最新推荐文章于 2024-01-03 13:19:56 发布
最新推荐文章于 2024-01-03 13:19:56 发布
阅读量336 收藏
点赞数
分类专栏： bug dubbo 文章标签： dubbo项目出现bug
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43666051/article/details/102913823
版权
dubbo 同时被 2 个专栏收录
6 篇文章 0 订阅
订阅专栏
bug
2 篇文章 0 订阅
订阅专栏 
com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method selAllStar in the service com.bjsxt.service.IStarService. Tried 3 times of the providers [192.168.54.1:20880] (1/1) from the registry 192.168.54.40:2181 on the consumer 192.168.54.1 using the dubbo version 2.5.7. Last error is: Failed to invoke remote method: selAllStar, provider: dubbo://192.168.54.1:20880/com.bjsxt.service.IStarService?anyhost=true&application=dubbo-consumer&check=false&dubbo=2.5.7&generic=false&interface=com.bjsxt.service.IStarService&methods=selAllStar&pid=185084&register.ip=192.168.54.1&remote.timestamp=1572929546153&side=consumer&timestamp=1572930853732, cause: Failed to send response: Response [id=2, version=2.0.0, status=20, event=false, error=null, result=RpcResult [result=[Star(id=1, name=zhangsan, age=12)], exception=null]], cause: java.lang.IllegalStateException: Serialized class com.bjsxt.pojo.Star must implement java.io.Serializable
java.lang.IllegalStateException: Serialized class com.bjsxt.pojo.Star must implement java.io.Serializable
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getDefaultSerializer(SerializerFactory.java:400)
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getSerializer(SerializerFactory.java:374)
	at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:381)
	at com.alibaba.com.caucho.hessian.io.CollectionSerializer.writeObject(CollectionSerializer.java:98)
	at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:383)
	at com.alibaba.dubbo.common.serialize.support.hessian.Hessian2ObjectOutput.writeObject(Hessian2ObjectOutput.java:79)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.encodeResponseData(DubboCodec.java:193)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encodeResponse(ExchangeCodec.java:269)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encode(ExchangeCodec.java:70)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.encode(DubboCountCodec.java:39)
	at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalEncoder.encode(NettyCodecAdapter.java:81)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:66)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:776)
	at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:304)
	at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99)
	at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:266)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
	at org.jboss.netty.channel.Channels.write(Channels.java:611)
	at org.jboss.netty.channel.Channels.write(Channels.java:578)
	at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:251)
	at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98)
	at com.alibaba.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:54)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:171)
	at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52)
	at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:81)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)


	at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)
	at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:229)
	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.selAllStar(proxy0.java)
	at com.bjsxt.AppTest.testStar(AppTest.java:21)
	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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to send response: Response [id=2, version=2.0.0, status=20, event=false, error=null, result=RpcResult [result=[Star(id=1, name=zhangsan, age=12)], exception=null]], cause: java.lang.IllegalStateException: Serialized class com.bjsxt.pojo.Star must implement java.io.Serializable
java.lang.IllegalStateException: Serialized class com.bjsxt.pojo.Star must implement java.io.Serializable
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getDefaultSerializer(SerializerFactory.java:400)
	at com.alibaba.com.caucho.hessian.io.SerializerFactory.getSerializer(SerializerFactory.java:374)
	at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:381)
	at com.alibaba.com.caucho.hessian.io.CollectionSerializer.writeObject(CollectionSerializer.java:98)
	at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:383)
	at com.alibaba.dubbo.common.serialize.support.hessian.Hessian2ObjectOutput.writeObject(Hessian2ObjectOutput.java:79)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.encodeResponseData(DubboCodec.java:193)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encodeResponse(ExchangeCodec.java:269)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encode(ExchangeCodec.java:70)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.encode(DubboCountCodec.java:39)
	at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalEncoder.encode(NettyCodecAdapter.java:81)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:66)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:776)
	at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:304)
	at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99)
	at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:266)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
	at org.jboss.netty.channel.Channels.write(Channels.java:611)
	at org.jboss.netty.channel.Channels.write(Channels.java:578)
	at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:251)
	at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98)
	at com.alibaba.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:54)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:171)
	at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52)
	at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:81)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.returnFromResponse(DefaultFuture.java:220)
	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:139)
	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:113)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:97)
	at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)
	at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
	at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:54)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
	at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
	at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)
	at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)
	at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)
	... 27 more

出错误原因是:pojo的实体类没有进行序列化

小小来也
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
dubbo-monitor-simple.zip
01-04
dubbo-monitor监控中心，基于alibaba dubbo.jar开发，解决Decode rpc invocation failed: expected map/object at java.lang.String (Ljava/lang/String)、com.alibaba.dubbo.common.URL' could not be instantiated...
Invalid name=”com.alibaba.dubbo.config.ProtocolConfig#0″
12-22
java.lang.IllegalStateException: Invalid name=“com.alibaba.dubbo.config.ProtocolConfig#0” contains illegal character, only digit, letter, ‘-’, ‘_’ or ‘.’ is legal 原因: 如果没有指定id属性,...
dubbo:com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method 解决
热门推荐
china_bobo的专栏
12-27 4万+
本地启动了dubbo的provider，zk，consumer，在dubbo admin里看，service的状态也都正常。 但是服务消费的时候，一直报错：com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method 网上找了半天，有人说是因为类没有实现序列化，有的说是因为interface写的不一致导致的。 一一排查后 ，发
kingbase安全之强身份验证
最新发布
kingstone96888的博客
01-03 1362
¶。
dubbo常见报错：Failed to invoke the method in the service Tried 3 times of the providers的解决方法
qq_39933337的博客
04-15 5215
本地测试文件上传时，客户工程调用文件工程出现了此问题，网上找了一些方法但还是没有效果，经过不断地尝试，发现了这个原因，客户成工程和文件工程都是采用debug模式启动，后来将调用方客户工程采用run模式启动，发现可以正常调用其他的dubbo服务了。 ...
com.alibaba.dubbo.rpc.RpcException: Fail to start server
weixin_44502835的博客
08-01 436
com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.137.1:20880/com.leizhe.dubbo.demo.service.UserService?anyhost=true&application=user-consumer&bind.ip=192.168.137.1&bind.port=20880&channel.readonly.sent=true&amp.
解决com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.194.1:20880/...报错方案
HelloWorld998的博客
07-06 2万+
问题描述 当我在使用Dubbo整合SpringBoot时，启动完成provider[提供者]的服务后，再依次启动consumer[消费者]的服务时，发现以下报错： com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.194.1:20880/com.dream.gmall.se...
com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.16。。
weixin_30867015的博客
08-09 1026
开启了linux的zookeeper服务，启动e3-manager时发现出现com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.16...这个错误，网上的资料真是误导人啊，最后发现防火墙木有关，关掉就好了 systemctl stop firewalld.service setenforce 0 转...
dubbo.rpc.demo.rar；dubbo双模块RPC调用，附源码及编译后内容，解压即可用
07-07
dubbo.rpc.demo.rar；dubbo双模块RPC调用，附源码及编译后内容，解压即可用；dubbo.rpc.demo.rar；dubbo双模块RPC调用，附源码及编译后内容，解压即可用；dubbo.rpc.demo.rar；dubbo双模块RPC调用，附源码及编译后...
解决dubbo启动的时候报错，无法读取方案文档 'http://code.alibabatech.com/schema/dubbo/dubbo.xsd'
03-30
解决启动dubbo项目的时候出现，无法读取方案文档 'http://code.alibabatech.com/schema/dubbo/dubbo.xsd'，其实在你本地把dubbo.jar文件解压，然后在META-INF下边就有个dubbo.xsd，就是他
com.sun.jdmk.jmxtools.1.2.1 jmxtools-1.2.1.jar 亲测可用
12-14
缺少jar包 Description Resource Path Location Type Missing artifact com.sun.jdmk:jmxtools:jar:1.2.1 pom.xml Maven Dependency Problem jmxtools-1.2.1.jar
Java的dubbo.xsd配置文件
11-29
在Eclipse中配置Dubbo时，`dubbo.xsd`配置文件扮演着至关重要的角色。这个文件定义了Dubbo服务的所有配置元素和属性，遵循XML Schema（XSD）规范，确保XML配置文件的正确性和一致性。 `dubbo.xsd`文件包含了一系列...
dubbo.xsd 文件下载 ，dubbo 服务启动报异常，本地加载xsd文件
09-03
dubbo 启动服务远程找不到dubbo.xsd文件，不能够启动，本地直接加载xsd文件
nodejs使用原生的dubbo协议打通了dubbo的rpc方法调用.
08-09
标题中的“nodejs使用原生的dubbo协议打通了dubbo的rpc方法调用”意味着在Node.js环境中，开发者成功地实现了对Dubbo服务的RPC（远程过程调用）访问，利用了Dubbo协议的特性。Dubbo是阿里巴巴开源的一个高性能、轻量...
dubbo找不到dubbo.xsd报错
11-18
- schema_reference.4: Failed to read schema document 'http://code.alibabatech.com/schema/dubbo/dubbo.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root ...
com.alibaba.dubbo.rpc.RpcException 启动dubbo报错
明天和意外哪个先到，其实这不重要
01-09 5682
因为同一套代码要启两个服务，所以直接复制了一套，结果启动的时候一个启动成功了，一个报错，dubbo的异常，后来看了一下是dubbo的端口号绑定异常 SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoad...
Failed to invoke the method $invoke in the service com.***GenericService. Tried 3 times of the provi
weixin_44876207的博客
05-19 4323
泛化调用报错： 先贴错误 Exception in thread “main” com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method $invoke in the service com.alibaba.dubbo.rpc.service.GenericService. Tried 3 times of the providers [10.2.7.5:20880] (1/1) from the registry 10.2.0.201:
Failed to invoke the method subscribe in the service com.alibaba.dubbo.registry.RegistryService
好好学java
07-28 8436
1 异常信息 今天在写 dubbo 文章的时候遇到一个问题，倒是折腾了几分钟，百思不得其解，最后终于发现了。异常信息如下： com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method subscribe in the service com.alibaba.dubbo.registry.RegistryService. Tried...
【Dubbo调用服务超时】Failed to invoke the method ……
M_hhxc的博客
09-13 1067
SpringBoot整合Dubbo超时报错：远程调用服务超时
com.alibaba.dubbo.rpc. RpcException: Failed to invoke the method getById in the service com.gxa.nj.service.UserCardService.
07-28
- *2* *3* [com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method list in the service com.dream.servic](https://blog.csdn.net/Astudies/article/details/105053109)[target="_blank" data-report-...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值