After we got reported that the epoll(..) workaround was a way to aggressive (because of a bug) in our latest release we thought it would be time to cut another one which fix the mentioned problem. So here you get it!
This mentioned epoll(..) bug can lead to very excessive cpu-spinning, which will most likely produce 100% cpu usage on the core that runs the thread of the NioWorker or NioDatagramWorker. For more informations please see #327, #565.
The workaround is disabled by default at the moment. This is because we want to be sure its "mature" enough before enable it by default. Anyway, if you got hit by the bug enable the workaround via the org.jboss.netty.epoolBugWorkaround System Property.
Another problem which was solved was only effecting Windows users most of the times, when using Netty on the client-side. Once you released the external resources you sometimes saw a ChannelException. This was an effect of a small race-condition which was present during checking for connection timeout and the release of the resources. This was fixed as part of #395.
For all of the other changes please checkout our issue tracker.
The JAR file can be found on Maven Central or you can also get the full tarball from the download page. Whatever you prefer...
Please let us know if you have any problems or questions.
Enjoy coding, and sorry for the "buggy" 3.5.6.Final release before!