There is no error on the duubo server and the client reports an error

Problem phenomenon:
When the dubbo consumer calls the server, the server does not have an error log. All the calls are successful, but the consumer reports an error. This kind of error occurs infrequently.


Reason:
There is an invoke process when the dubbo client calls the server. In the invoke process, there are many proxy classes and automatically generated classes that shield the client from a lot of call details, such as resume sokect connections and deserialize tcp messages. Errors in this process are generally not encountered, and they are more difficult to solve after encountering them.
We encountered this error because the server team used the classes in the jar json-lib to pass data, and the version of the jar package it indirectly referenced was inconsistent with the version we referenced internally. This leads to the fact that the data serialized by the server cannot be correctly deserialized into a json-lib object during the invoke process (individual data is relatively individual), and the above error occurs as a result.

When the client team executes the server-side call, an error is reported, and the server-side cannot see the error log! I won't post the company's privacy log, and everyone should follow this line of thinking when this phenomenon occurs.