Major Description
If a custom key is used for cache values then the following scenario doesn't work:
- value is placed on C++ side;
- value is read on Java side (value is not found here).
Reverse direction is not workable as well.
HashCode is implemented properly in C++ and Java.
Fast debugging showed that a partition and primary node is calculated properly. Looks like that there is a serialization related issue that leads to the situation when "equals" fails during an object lookup.