Netty 4.2.2.Final released
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 (#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 dependencies as the old version did not correctly handle ByteBuffer that have an arrayOffset > 0 (#15146)
- Kqueue: Fix registration failure when fd is reused (#15150)
- Fix incorrect assignment of SingleThreadIoEventLoop constructor (#15155)
- Fix signing keys with ML-DSA in CertificateBuilder (#15156)
- Optimize ByteBuf.setCharSequence for adaptive allocator (#15165)
- IoUring: Providing Unix Domain Socket Support for IoUring (#15210)
- Ensure OpenSsl.availableJavaCipherSuites does not contain null value (#15215)
- Make JdkZlibEncoder accept Deflater.DEFAULT_COMPRESSION as level (#15217)
- Add API to wrap virtual thread task for FastThreadLocal support (#15222)
- Introduce ByteBuf.readString method (#15224)
- Add support for creating direct ByteBuffers from MemorySegments (#15231)
- Always prefer direct buffers for pooled allocators if not explicit disabled (#15232)
- Update to netty-tcnative 2.0.72.Final (#15240)
- IoUring:properly handle ERRNO_ECANCELED_NEGATIVE in splice (#15250)
- Fix netty-buffer OSGi metadata (#15274)
- Kqueue: Delay removal from registration map to fix noisy warnings (#15279)
- StreamBufferingEncoder doesn't work when settings auto-ack is disabled (#15301)
- Add SETTINGS_ENABLE_CONNECT_PROTOCOL to the default HTTP/2 settings (#15312)
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