Mastering TCP Sticky Packets: Causes, Scenarios, and Netty Solutions

Sticky Packet and Unpacking in TCP

TCP is a byte‑stream protocol; it does not preserve message boundaries. When the sender transmits several small messages, the operating system may coalesce them into a single TCP segment, causing a sticky packet . Conversely, if a single message exceeds the OS buffer size (commonly 1024 bytes), TCP splits it into multiple segments, resulting in unpacking . Because UDP preserves datagram boundaries, these phenomena occur only with TCP.

Typical Scenarios

Ideal case – each message fits the buffer or respects the timeout, so the messages are sent separately.

Sticky packet – two or more small messages arrive close together; the OS merges them into one TCP segment.

Unpacking – a large message exceeds the buffer and is divided into several TCP segments.

Combined – a large message is split, and the leftover fragment merges with the next message, producing both effects.

Common Framing Solutions

Fixed‑length framing : Pad every message to a predetermined size (e.g., 100 bytes) using zeros or spaces.

Delimiter‑based framing : Append a special delimiter such as \r\n to each message; the receiver reads until the delimiter is encountered (e.g., FTP).

Length‑field framing : Include the total length of the message in a header; the receiver first reads the length field and then reads exactly that many bytes.

Custom protocol : Design a protocol that explicitly defines framing, delimiters, and length fields.

Netty Decoders for Framing

Netty provides reusable decoder components that implement the above strategies: LineBasedFrameDecoder – splits data based on line‑ending characters. DelimiterBasedFrameDecoder – splits data using a configurable delimiter. FixedLengthFrameDecoder – splits data into frames of a fixed size. LengthFieldBasedFrameDecoder – parses a length field in the message header; this is the most widely used approach for high‑concurrency, high‑throughput systems because it avoids unnecessary padding.

Key Takeaway

Because TCP delivers a continuous byte stream, application‑level protocols must define explicit message boundaries (framing) to avoid sticky‑packet and unpacking problems. Selecting an appropriate framing method—fixed length, delimiter, or length field—and using the corresponding Netty decoder (or a custom implementation) ensures reliable message parsing in TCP‑based communication such as RPC frameworks.