Fix InputStream deserialization bug #76
Open
+206
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@AlbumenJ This code cannot completely solve the problem of deserializing InputStream:Fix input stream unable to being deserialized #14837
The code before modification is:
In
in.readInputStream()
, he only readInputStream
oftag
, and his data was not read. This will cause an error in the '_offset' whenorg.apache.dubbo.rpc.protocol.dubbo.DecodeableRpcResult#decode(org.apache.dubbo.remoting.Channel, java.io.InputStream)
reads the map in thehandleAttachment(in);
method, throwing an exception;So when deserializing InputStream, it is necessary to read its bytes and move _osffet to the correct position.
related issues:方法返回InputStream时expected map/object at java.lang.String异常