Removed OP_WRITE event which is fired when a connection is closed - totally unnecessary not that we use different write prevention mechanism
This commit is contained in:
parent
6329cbe940
commit
891821788a
@ -605,10 +605,6 @@ class NioWorker implements Runnable {
|
||||
if (channel.setClosed()) {
|
||||
future.setSuccess();
|
||||
if (connected) {
|
||||
if (channel.getRawInterestOps() != Channel.OP_WRITE) {
|
||||
channel.setRawInterestOpsNow(Channel.OP_WRITE);
|
||||
fireChannelInterestChanged(channel, Channel.OP_WRITE);
|
||||
}
|
||||
fireChannelDisconnected(channel);
|
||||
}
|
||||
if (bound) {
|
||||
|
@ -173,11 +173,6 @@ class OioWorker implements Runnable {
|
||||
if (workerThread != null && currentThread != workerThread) {
|
||||
workerThread.interrupt();
|
||||
}
|
||||
|
||||
if (channel.getInterestOps() != Channel.OP_WRITE) {
|
||||
channel.setInterestOpsNow(Channel.OP_WRITE);
|
||||
fireChannelInterestChanged(channel, Channel.OP_WRITE);
|
||||
}
|
||||
fireChannelDisconnected(channel);
|
||||
}
|
||||
if (bound) {
|
||||
|
Loading…
x
Reference in New Issue
Block a user