hazelcast / hazelcast/hazelcast-csharp-client
[TRACKING ISSUE] Fix fragmented message handling [API-2076]
Open
Jira
Source: Tracking
- Dominant language
- C#
- Stars
- 107
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The tracking issue for the Java side PR.
**Fix fragmented message handling**
See https://github.com/hazelcast/hazelcast/pull/17084 for details.
---
By definition, fragmented messages may have arbitrary number of frames.
However, ClientMessageDecoder was using ClientMessage#createForDecode
which expects a single frame that has no next frame. As the added test
shows, that assumption generally does not hold. Start frame of the
fragmented message may have next frames. The fix correctly creates
a client message using the start and end frames of the fragmented
message.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.