Go to file
Norman Maurer 62bbd4220a Fix JVM segfault during JNI call. Part of [#2647]
Motivation:
Currently when Native.writev(...) is used it is possible to see a JVM segfault because the offset is updated to early.

Modification:
Only update the offset once it is safe to do so.

Result:
No more segfault
2014-07-09 13:34:15 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
buffer [#2642] CompositeByteBuf.deallocate memory/GC improvement 2014-07-08 21:08:14 +02:00
codec [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-dns [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-http Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:37:10 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
common [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:37:10 +02:00
handler [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
license Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
microbench [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 12:21:58 +02:00
transport [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-native-epoll Fix JVM segfault during JNI call. Part of [#2647] 2014-07-09 13:34:15 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26: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:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
pom.xml Add missing m2eclipse life cycle mapping 2014-07-06 16:53:29 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +09:00

Netty Project

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

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.