huisman6 opened a new issue, #15737: URL: https://github.com/apache/dubbo/issues/15737
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo 3.3.5 , JDK21**** ### Steps to reproduce this issue **Backgroud** The default implementation of org.apache.dubbo.common.serialize.ObjectOutput.writeEvent calls writeObject(data), The default implementation of org.apache.dubbo.common.serialize.ObjectInput.readEvent is readUTF(). We used apache dubbo-serialization-fury/fory, which requires that serialization and deserialization methods must be called in pairs. The serialization format and parsing logic of writeObject and readUTF are different, resulting in deserialization exceptions. The error stack is as follows: ``` java [DUBBO] Decode request failed: Decode dubbo protocol event failed. java.io.IOException: org.apache.dubbo.common.serialize.SerializationException: java.lang.IndexOutofBoundsException: readerindex(6) + length(67108837) exceeds size(32): org.apache.fory.memory.MemoryBuffer$BsoundChecker@52b2d461 ``` **How to reproduce:** 1. add maven dependency dubbo-serialization-fury or dubbo-serialization-fory 2. call：ForyObjectInput.writeEvent("R") and ForyObjectInput.readEvent() ### What you expected to happen The default implementation logic of oObjectOutput.writeEvent and ObjectInput.readEvent remains consistent, and the default implementation of writeEvent is adjusted to writeUTF(String). ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
