andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,002 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
2443005c15
Go to file
Trustin Lee 2443005c15 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-14 17:50:31 +09:00
all [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
buffer Disable caching of PooledByteBuf for different threads. 2014-09-22 13:38:35 +02:00
codec Add support for ExtensionRegistryLite in ProtobufDecoder 2014-09-15 07:06:30 +02:00
codec-http Add verification for websocket subprotocol on the client side. 2014-10-14 14:47:11 +09:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
common Fix a bug in NetUtil.createByteArrayFromIpAddressString() 2014-10-14 17:50:31 +09:00
example Adding a benchmark for websockets 2014-10-13 07:13:56 +02:00
handler Change the operator order of TrafficCounter to calculate the throughput to get the correct result 2014-10-01 06:45:17 +02:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
testsuite Fix buffer leak in DatagramUnicastTest caused by incorrect usage of CompositeByteBuf 2014-09-10 11:40:53 +02:00
transport Do not consider PortUnreachableException to require channel closure 2014-10-14 17:50:31 +09:00
transport-native-epoll Add AbstractUnsafe.annotateConnectException() 2014-10-14 17:50:31 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09: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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09: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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.