Skip navigation

Netty 4.1.114.Final released

by normanmaurer
on

We are happy to announce the release of netty 4.1.114.Final. This is a bug-fix release.

The most important changes are:

  • Validate HTTP Method (#14280)
  • Release AdaptiveByteBuf when ownership could not be transfered. (#14285)
  • Make arenas reuse their last chunk more aggressively (#14291)
  • Only add Magazine to Set if we can ensure its removed again (#14292)
  • Ensure Chunk will not leak if init of AdaptiveByteBuf fails for whatever reason (#14295)
  • Correctly release one-off allocated chunks (#14302)
  • Ensure pooled memory is released when AdaptivePoolingAllocator is GC'ed (#14304)
  • Slices / duplicates of AdaptiveByteBuf must not escape the rootParent (#14310)
  • Fix sizeBucket bug in AdaptivePoolingAllocator (#14311)
  • AdaptiveByteBufAllocator: More strict reference counting for chunks (#14322)
  • Ensure we not store the DnsQueryContext for later removal when we couldnt obtain a query id (#14326)
  • Reduce memory fragmentation (#14333)
  • Properly free magazine chunks and avoid orphaned magazines (#14334)
  • Magazines must be freed under the expand lock (#14336)
  • Release message before failing promise when multiple requests are written while upgrade is in progress. (#14342)
  • Allow to reuse more then one session per host / port mapping (#14356)
  • Ensure writes will not fail when triggered after receiving UpgradeEvent.UPGRADE_SUCCESSFUL (#14362)
  • Refactor DnsNameResolver to be able to use different strategies when it comes to creating Channels for queries. (#14374)
  • DnsNameResolver: allow users to skip bind() during bootstrap (#14375)
  • DnsResolverBuilder methods should make it clear that these are for DatagramChannel (#14379)

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.