Hello, Can you please share your stacktrace? In 2.7.6 I think this bug affects only cache configuration retrieval and binary metadata retrieval. To avoid problems with binary metadata retrieval you should not use types which typeId (IgniteClient.binary().typeId()) starts with byte 103 as cache keys or values.
If you can't upgrade Ignite server to 2.9.1, perhaps you can upgrade only the client? This will also solve the problem. ср, 27 янв. 2021 г. в 19:46, maxi628 <[email protected]>: > Hello everyone. > > I'm having an issue that appears randomly on my internal product testing. > Looks like its related to > https://issues.apache.org/jira/browse/IGNITE-13401 > but the stacktrace looks different. > Basically I'm building a BinaryObject which ends up fetching > BinaryObjectMetadata from the server and it fails with that exception. > > > > Upgrading to ignite 2.9.1 where it's patched isn't an option for me. > The BinaryObjectMetadata is user-configured via some interfaces. > Is there any workarounds for this? > If we have a way to calculate the size of the metadata before sending it we > could add a dummy field in those cases where it ends up matching the > GridBinaryMarshaller.OBJ on the second byte of the stream. > > Here's the datagram in hex > > > And a photo from the debugger in which it shows the problematic value > > Screen_Shot_2021-01-27_at_10.png > < > http://apache-ignite-users.70518.x6.nabble.com/file/t3058/Screen_Shot_2021-01-27_at_10.png> > > > Thanks everyone. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
