From 1142a1aa062ec85ca3d2f3465afdaee56fff586b Mon Sep 17 00:00:00 2001
From: Trustin Lee <trustin@gmail.com>
Date: Sat, 9 Jan 2010 08:54:21 +0000
Subject: [PATCH] Fixed a cosmetic problem in NioDatagramWorker.read() - In
 some platform, ClosedChannelException is raised on DatagramChannel.receive()
 depending on timing, and it's safe to ignore.

---
 .../org/jboss/netty/channel/socket/nio/NioDatagramWorker.java   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main/java/org/jboss/netty/channel/socket/nio/NioDatagramWorker.java b/src/main/java/org/jboss/netty/channel/socket/nio/NioDatagramWorker.java
index 3725e0b570..c676c39386 100644
--- a/src/main/java/org/jboss/netty/channel/socket/nio/NioDatagramWorker.java
+++ b/src/main/java/org/jboss/netty/channel/socket/nio/NioDatagramWorker.java
@@ -401,7 +401,7 @@ class NioDatagramWorker implements Runnable {
             // the channel is ready to receive.
             remoteAddress = nioChannel.receive(byteBuffer);
             failure = false;
-        } catch (AsynchronousCloseException e) {
+        } catch (ClosedChannelException e) {
             // Can happen, and does not need a user attention.
         } catch (Throwable t) {
             fireExceptionCaught(channel, t);