You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] The default implementations of Dubbo ObjectOutput.writeEvent and ObjectInput.readEvent are inconsistent, resulting in abnormal functionality of some serialization components. #15737
I am sure that all the content I provide is in English.
Search before asking
I had searched in the issues 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.
add maven dependency dubbo-serialization-fury or dubbo-serialization-fory
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!
Activity
finefuture commentedon Oct 23, 2025
Would you like to submit a PR to fix it?
Fix inconsistent writeEvent and readEvent in default serialization (a…