Dubbo序列化与反序列化问题、服务端获取到的请求参数类型转换异常（变成了Map类型的对象）

IccBoY

已于 2023-04-22 10:36:26 修改

阅读量1.7k

点赞数

分类专栏： Java 后端问题文章标签： dubbo java 开发语言

于 2023-02-14 10:27:26 首次发布

本文链接：https://blog.csdn.net/ccboy2009/article/details/129021958

版权

后端同时被 3 个专栏收录

23 篇文章 3 订阅

订阅专栏

Java

22 篇文章 0 订阅

订阅专栏

问题

13 篇文章 0 订阅

订阅专栏

java.io.StreamCorruptedException: invalid stream header: 77D30000 ; Decode rpc invocation failed

现象

2023-02-14 09:49:32.251 [NettyServerWorker-4-2] [] [WARN] o.a.d.r.exchange.codec.ExchangeCodec-130  [DUBBO] Skip input stream 634, dubbo version: 2.7.0, current host: 10.10.1.44
2023-02-14 09:49:36.858 [NettyServerWorker-4-1] [] [WARN] o.a.d.r.p.d.DecodeableRpcInvocation-73  [DUBBO] Decode rpc invocation failed: invalid stream header: 77D30000, dubbo version: 2.7.0, current host: 10.10.1.44
java.io.StreamCorruptedException: invalid stream header: 77D30000
        at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:899)
        at java.io.ObjectInputStream.<init>(ObjectInputStream.java:357)
        at org.apache.dubbo.common.serialize.java.JavaObjectInput.<init>(JavaObjectInput.java:33)
        at org.apache.dubbo.common.serialize.java.JavaSerialization.deserialize(JavaSerialization.java:47)
        at org.apache.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:91)
        at org.apache.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:70)
        at org.apache.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody(DubboCodec.java:132)
        at org.apache.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:125)
        at org.apache.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:85)
        at org.apache.dubbo.rpc.protocol.dubbo.DubboCountCodec.decode(DubboCountCodec.java:46)
        at org.apache.dubbo.remoting.transport.netty4.NettyCodecAdapter$InternalDecoder.decode(NettyCodecAdapter.java:95)
        at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:501)
        at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:440)
        at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
        at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
        at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
        at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)

解决

配置 dubbo.protocol.serialization 的值在客户端和服务端保持一致。
在这里插入图片描述
https://dubbo.apache.org/zh-cn/docs3-v2/java-sdk/reference-manual/protocol/dubbo/#%E7%89%B9%E6%80%A7%E8%AF%B4%E6%98%8E

Transporter: mina, netty, grizzy
Serialization: dubbo, hessian2, java, json
Dispatcher: all, direct, message, execution, connection
ThreadPool: fixed, cached

Serialization

Dubbo 序列化,未开发成熟
hessian2 , Thrift 之前使用的,是一种跨语言的高效二进制序列化方式
json序列化:目前两种,一种是阿里的 fastjson 库,另一种是采用 dubbo 中自己实现的简单 json 库,建议使用 jkson
Java序列化:主要采用JDK自带的Java序列化实现,性能很不理想
针对Java语言的:Kryo, FST等等 Kryo是一种非常成熟的序列化实现,已经在Twitter\Groupon\Yahoo以及多个著名开源项目(如Hive\Storm)中广泛使用.FST则较新,缺乏足够多的成熟案例
跨语言的:Protostuff, ProtoBuf, Thrift, Avro, MsgPack等等

服务端获取导入的入参变成了Map类型的对象

现象：

dubbo的接口

public interface PersonApi {
	void addUser(Request<PersonDTO> req);
}

@Data
public class Request<T> {
	private String invokeId;
	private T data;
}

@Data
public class PersonDTO {
	private String userName;
	private Integer age;
}

public class StudentDTO extends PersonDTO {
	private String className;
}

客户端调用


public class Demo {
		
	@Reference
	private PersonApi personApi;
	
	// 正常调用
	public void normalInvoke() {
		PersonDTO person = new PersonDTO();
		person.setName("IccBoY");
		person.setAge(20);
		Request<PersonDTO> req = new Request<PersonDTO>();
		req.setData(person);
		personApi.addUser(req);
	}
	// 上面这种方式服务端可以正常获取对象

	// 通过子类调用
	public void normalInvoke() {
		PersonDTO person = new StudentDTO();
		person.setName("IccBoY");
		person.setAge(20);
		person.setClassName("一班");
		Request<PersonDTO> req = new Request<PersonDTO>();
		req.setData(person);
		personApi.addUser(req);
	}
	// 上面这种方式，服务端 打印req日志正常，但是调用 PersonDTO person = req.getData() 时，报类型转换异常
}