andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

A workaround for 100% CPU consumption issue in NIO selectors, suggested by David M. Lloyd

Browse Source
This commit is contained in:
Trustin Lee 2009-10-26 16:41:56 +00:00
parent dabea9dfff
commit 52221931d5
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/java/org/jboss/netty/channel/socket/nio/NioDatagramWorker.java
View File

@ -339,7 +339,7 @@ class NioDatagramWorker implements Runnable {
i.remove(); i.remove();
try { try {
int readyOps = k.readyOps(); int readyOps = k.readyOps();
if ((readyOps & SelectionKey.OP_READ) != 0) { if ((readyOps & SelectionKey.OP_READ) != 0 || readyOps == 0) {
if (!read(k)) { if (!read(k)) {
// Connection already closed - no need to handle write. // Connection already closed - no need to handle write.
continue; continue;

2
src/main/java/org/jboss/netty/channel/socket/nio/NioWorker.java
View File

@ -271,7 +271,7 @@ class NioWorker implements Runnable {
i.remove(); i.remove();
try { try {
int readyOps = k.readyOps(); int readyOps = k.readyOps();
if ((readyOps & SelectionKey.OP_READ) != 0) { if ((readyOps & SelectionKey.OP_READ) != 0 || readyOps == 0) {
if (!read(k)) { if (!read(k)) {
// Connection already closed - no need to handle write. // Connection already closed - no need to handle write.
continue; continue;