Skip to content
Snippets Groups Projects
Select Git revision
  • 4.1 default protected
  • master
  • ssl_cache_revamp
  • ssl_cache_again
  • inflater_jdk11
  • brotli-decompressor
  • io-uring
  • benchmark
  • compile_workaround_iouring
  • writev_iouring
  • fix_prop_name
  • unlink_handler
  • handler_removed
  • ignore_header_data_wip
  • drop-npn
  • 4.0
  • writability
  • 3.10
  • master_deprecated
  • 3.9
  • netty-4.1.59.Final
  • netty-4.1.58.Final
  • netty-4.1.57.Final
  • netty-4.1.56.Final
  • netty-4.1.55.Final
  • netty-4.1.54.Final
  • netty-4.1.53.Final
  • netty-4.1.52.Final
  • netty-4.1.51.Final
  • netty-4.1.50.Final
  • netty-4.1.49.Final
  • netty-4.1.48.Final
  • netty-4.1.47.Final
  • netty-4.1.46.Final
  • netty-4.1.45.Final
  • netty-4.1.44.Final
  • netty-4.1.43.Final
  • netty-4.1.42.Final
  • netty-4.1.41.Final
  • netty-4.1.40.Final
40 results

netty

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Norman Maurer authored
    Motivation:
    
    ExecutorService.invoke*(...) methods may block by API definition. This can lead to deadlocks if called from inside the EventLoop in SingleThreadEventExecutor as it only has one Thread that does all the work.
    
    Modifications:
    
    Throw a RejectedExectionException if someone tries to call SingleThreadEventExecutor.invoke*(...) while in the EventLoop.
    
    Result:
    
    No more deadlock possible.
    438b29fd
    History

    Netty Project

    Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

    Links

    How to build

    For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

    You require the following to build Netty:

    Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

    Branches to look

    Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.