Netty Project

We are happy to announce the release of netty 4.1.123.Final. This is a bug-fix release but also contains various performance enhancements in the AdaptiveByteBufAllocator. The most important changes are: Fix chunk reuse bug in adaptive allocator ... [More] (#15428) More accurate adaptive memory usage accounting (#15425) Introduce size-classes for the adaptive allocator (#15414) Reduce magazine proliferation eagerness (#15422) Fix concurrent ByteBuffer access issue in AdaptiveByteBuf.getBytes (#15410) Fix possible buffer corruption caused by incorrect setCharSequence(...) implementation (#15393) AdaptiveByteBuf: Fix AdaptiveByteBuf.maxFastWritableBytes() to take writerIndex() into account (#15376) Optimize capacity bumping for adaptive ByteBufs (#15368) AbstractDnsRecord: equals() and hashCode() to ignore name field's case (#15330) Backport Unsafe guards (#15346) Guard recomputed offset access with hasUnsafe (#15357) HTTP2: Always... [Less]

We are happy to announce the release of netty 4.2.3.Final. We put a lot of work into this release so please ensure to read on for all the changes / bugfixes / performance improvements. The most important changes are: IoUring: Correctly refetch ... [More] completions that were produced because of inline submissions (#15480) IoUring: Explicit set CQSIZE by default and use a much saner default for submission ring (#15477) IoUring: Allow to configure what allocation strategy the buffer ring (#15469) IoUring: Add IoUringBufferRingConfig.Builder (#15453) Add property to turn off pinned memory tracker in PoolChunk (#15436) Add JFR events for PooledByteBufAllocator (#15433) More accurate adaptive memory usage accounting (#15423) Fix chunk reuse... [Less]

We are happy to announce the release of netty-incubator-codec-quic 0.0.73.Final. This is a bug-fix release but also upgrades its quiche version to fix CVE-2025-4820 and CVE-2025-4821. Because of this we highly recommend to upgrade as soon as ... [More] possible. The most important changes are: Cleanup code to make stacktrace less confusing (#796) Update to latest boringssl sha (#794) Fix crash in Quiche when calling isClosed on freed connections (#798) Fix incorrect handling of stream capacity greater than 232 (#806) Obtain correct cipher to generate the authentication method (#809) Update to netty 4.1.122.Final (#810) Update to quiche 0.24.4 (#811) For more details related to this release see our bug-tracker. For more... [Less]

We are happy to announce the release of netty 4.2.2.Final. This is our second release for the 4.2 release train, including bug-fixes, performance enhancement and new features. The most important changes are: Graduate HTTP/3 from incubator ... [More] (#15048) Allows manually running tasks with timeout (in ns) (#15124) Port over fix for crash in QUIC codec (in ns) (#15130) Fix concurrent ByteBuf write access bug in adaptive allocator (#15131) IoUring: Allow users to explicit enable RECVSEND_BUNDLE support (#15135) Make EmbeddedChannel ticker configurable (#15141) IoUring: Don't depend on the fact that ByteBuf.memoryAddress() works (#15142) Always correctly calculate the memory address of the ByteBuf even if sun.misc.Unsafe is not usable (#15143) Upgrade lz4... [Less]

We are happy to announce the release of netty 4.1.122.Final. This is a bug-fix release. The most important changes are: DirContextUtils.addNameServer(...) should just catch Exception internally (#15108) Make public API specify explicit ... [More] maxAllocation to prevent OOM (#15122) Fix concurrent ByteBuf write access bug in adaptive allocator (#15132) Fix transport-native-kqueue Bundle-SymbolicNames (#15075) Fix resolver-dns-native-macos Bundle-SymbolicNames (#15076) Always correctly calculate the memory address of the ByteBuf even if sun.misc.Unsafe is not usable (#15144) Upgrade lz4 dependencies as the old version did not correctly handle ByteBuffer that have an arrayOffset > 0 (#15147) Optimize ByteBuf.setCharSequence for adaptive allocator (#15170) Kqueue: Fix registration failure when fd is reused (#15162) Make JdkZlibEncoder accept Deflater.DEFAULT_COMPRESSION as level... [Less]

We are happy to announce the release of netty 4.2.1.Final. This is our first bug-fix release for the 4.2 release train. The most important changes are: Add necessary native-image configuration files (#14928) Graduate the QUIC codec from incubator ... [More] to Netty Core (#14979) IoUring: Share IovArray to reduce jitter and allocations (#14996) Optionally depend on bctls-jdk15on, take 2 (#14998) Fix the issue where pendingTimeouts may be incorrect in the HashedWheelTimer (#15000) SSL: Clear native error if named group is not supported (#15001) ManualIoEventLoop: Correctly calculate delayNanos and deadlineNanos (#15002) Make public API specify explicit maxAllocation to prevent OOM (#15005) fix: Crash early on custom native workdir failure (#15009) Add support for ML-KEM... [Less]

We are happy to announce the release of netty-incubator-codec-quic 0.0.72.Final. This is a bug-fix release. The most important changes are: Update to netty 4.1.121.Final (#792) Correctly detect supported namedGroups during initialization (#791) ... [More] CEnsure we don't directly close the stream if we receive a STOP_SENDING frame as there might be data that was not read / processed yet. (#790) For more details related to this release see our bug-tracker. For more details about this codec in general please read our initial announcement. Thank You Every idea and bug-report counts, and so we thought it is worth mentioning those who helped in this area. Please report an unintended omission. @chrisvest @normanmaurer... [Less]

We are happy to announce the release of netty 4.1.121.Final. We did a quick followup release as something went wrong during our release of 4.1.120.Final yesterday and so required a different GLIBC version as expected when using our native transport. ... [More] The most important changes are: Epoll.isAvailable() returns false on Ubuntu 20.04/22.04 arch amd64 (#15073) Fix transport-native-epoll Bundle-SymbolicNames (#15068) For more details please visit our bug tracker Thank You Every idea and bug-report counts, and so we thought it is worth mentioning those who helped in this area. Please report an unintended omission. @normanmaurer @rovarga @violetagg... [Less]

We are happy to announce the release of netty 4.1.120.Final. This is a bug-fix release. The most important changes are: Fix flawed termination condition check in HttpPostRequestEncoder#encodeNextChunkUrlEncoded(int) for current InterfaceHttpData ... [More] (#14799) Exposed decoderEnforceMaxConsecutiveEmptyDataFrames and decoderEnforceMaxRstFramesPerWindow (#14892) ThreadExecutorMap must restore old EventExecutor (#14899) Make Recycler virtual thread friendly (#14892) Disable sun.misc.Unsafe by default on Java 24+ (#14943) Adaptive: Correctly enforce leak detection when using AdaptiveByteBufAllocator (#14949) Add suppressed exception to original cause when calling Future.sync* (#14985) Add SETTINGS_ENABLE_CONNECT_PROTOCOL to the default HTTP/2 settings (#14995) Correct computation for suboptimal chunk retirement probability (#15014) Fix bug in method AdaptivePoolingAllocator.allocateWithoutLock(...) (#15032) Fix a Bytebuf leak in TcpDnsQueryDecoder (#15035) SSL: Clear native error if named group is not... [Less]

After a lot of work and many contributions from our OSS community we are thrilled to finally announce the release of netty 4.2.0.Final! Everyone using netty 4.1.x should be able to upgrade to 4.2.0.Final without any API breakage. The only new ... [More] requirement is JDK8 or later (and JDK9+ for io_uring) and a more recent GLIBC version when using our native transports. With the release of netty 4.2.0.Final we will also start to only merge bug-fixes into 4.1, new features will only be merged to 4.2 and main branches. While 4.1.x releases will only receive bug-fixes we will still support it 4.1.x... [Less]