Hotrod client tries to read one byte to much when Multimap returns KeyDoesNotExist ---------------------------------------------------------------------------------- Key: ISPN-12596 URL: https://issues.redhat.com/browse/ISPN-12596 Project: Infinispan Issue Type: Bug Components: Hot Rod Affects Versions: 12.0.0.Dev07, 11.0.8.Final Reporter: Stephan Köll Assignee: Dan Berindei Priority: Major Fix For: 12.0.0.Final When using a mutimap.get(key) and the key is not in the multi map, a warning is printed: {{WARN [org.infinispan.HOTROD] (HotRod-client-async-pool-4-16) ISPN004098: Closing connection [...] due to transport error: org.infinispan.client.hotrod.exceptions.InvalidResponseException:: ISPN004003: Invalid magic number. Expected 0xa1 and received 0x0 ?}}   This message could be traced back to here: [https://github.com/infinispan/infinispan/blob/12.0.0.Dev07/client/hotrod-...] the package looks like: /_magic:_/0xA1, /_VLong:messageId:_/0x22, /_GET_MULTIMAP_RESPONSE:_/0x68, /_OperationStatus.KeyDoesNotExist:_/0x02, /_no topology change:_/0x00, /_???_/0x00 The problem is the extra 0x00 (compare to the warning) The "extra bytes" are the results size, in the case of "NOT_EXIST" 0 [https://github.com/infinispan/infinispan/blob/12.0.0.Dev07/server/hotrod/...] But in the *KeyDoesNotExist* case Multimap does not read the extra bytes. Related Issue: https://issues.redhat.com/browse/ISPN-11630  Most likely introduced while fixing that issue: [https://github.com/infinispan/infinispan/commit/70f40926971d4769b24b13c1b...]     Related Chat: https://infinispan.zulipchat.com/#narrow/stream/118645-infinispan/t...