andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,255 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
75ed693794
Go to file
Trustin Lee 75ed693794 Do not consider PortUnreachableException to require channel closure 
Motivation:

When a datagram packet is sent to a destination where nobody actually listens to,
the server O/S will respond with an ICMP Port Unreachable packet.
The ICMP Port Unreachable packet is translated into PortUnreachableException by JDK.
PortUnreachableException is not a harmful exception that prevents a user from sending a datagram.
Therefore, we should not close a datagram channel when PortUnreachableException is caught.

Modifications:

- Do not close a channel when the caught exception is PortUnreachableException.

Result:

A datagram channel is not closed unexpectedly anymore.
2014-10-16 17:06:12 +09:00
all Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
buffer Disable caching of PooledByteBuf for different threads. 2014-09-22 13:39:42 +02:00
codec Fixing bugs in HTTP/2 pipeline exception handling 2014-09-30 16:31:42 -07:00
codec-dns Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-http2 HTTP/2 Server Example Not Using Flow Controller 2014-10-13 13:44:31 +02:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-mqtt Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-stomp Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
common Fix a bug in NetUtil.createByteArrayFromIpAddressString() 2014-10-14 12:33:44 +09:00
example Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
handler Change the operator order of TrafficCounter to calculate the throughput to get the correct result 2014-10-01 06:42:41 +02:00
handler-proxy Finish porting netty-proxy module 2014-10-14 12:46:35 +09:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench IPv6 address to string rfc5952 2014-09-22 20:30:14 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Shutdown Executor on MultithreadEventLoopGroup shutdown. Fixes #2837 2014-09-12 12:17:29 +09:00
transport Do not consider PortUnreachableException to require channel closure 2014-10-16 17:06:12 +09:00
transport-native-epoll Finish porting netty-proxy module 2014-10-14 12:46:35 +09:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Shutdown Executor on MultithreadEventLoopGroup shutdown. Fixes #2837 2014-09-12 12:17:29 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh ALPN java implementation 2014-08-30 13:41:07 -04:00

README.md

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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.