Replies: 1 comment
-
|
check latest dubbo to ensure it's ok, and compare it with dubbo 3.2.18 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-check
Apache Dubbo Component
Java SDK (apache/dubbo)
Details
Both the client and server dubbo versions are 3.2.18, and neither shows the configuration serialization protocol
Service interface definition:
public RpcResult<Date> businessMaxAuthTime(Caller caller, UserBusinessAuthRequest request)The client call will error:
java.lang.ClassCastException: java.time.LocalDateTime cannot be cast to java.util.DateBy arthas monitoring call status
Service server returns:
The result received by the client:
As you can see, the data type has changed from Timestamp to LocalDateTime, but if you downgrade the client's dubbo version to 3.0.12, then the return type received by the client is Timestamp, which is normal.
My question is whether dubbo3.2.18 has made any changes to anti-sequencing that caused the type conversion issue? How can I fix it in version 3.2.18?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions