WARN KQueueEventLoop - events[[1, 88, -1]]=[[1, 88, -1], {}] had no channel!

Expected behavior

No warning 2019-02-06 23:05:16.068 [KQueueEventLoopGroup-2-2] WARN i.n.channel.kqueue.KQueueEventLoop - events[[1, 88, -1]]=[[1, 88, -1], {}] had no channel!

Actual behavior

Unexpected warning when client application kill -9 or reset peer 2019-02-06 23:05:16.068 [KQueueEventLoopGroup-2-2] WARN i.n.channel.kqueue.KQueueEventLoop - events[[1, 88, -1]]=[[1, 88, -1], {}] had no channel!

Not received reset peer exception in exceptionCaught(ChannelHandlerContext ctx, Throwable cause) when interrupt client socket

Steps to reproduce

Run snippet code below and kill client

Minimal yet complete reproducer code (or URL to code)

public class ClientKQueue {

public static void main(String[] args) throws Exception {
    Bootstrap clientBootstrap = new Bootstrap()
        .channel(KQueueSocketChannel.class).group(new KQueueEventLoopGroup())
        .handler(new ChannelInboundHandlerAdapter());
    Channel channel = clientBootstrap.connect("localhost", 8080).awaitUninterruptibly().channel();

    channel.closeFuture().awaitUninterruptibly();
}

}

public class ServerKQueue {

public static void main(String[] args) {
    ServerBootstrap serverBootstrap = new ServerBootstrap()
        .channel(KQueueServerSocketChannel.class).group(new KQueueEventLoopGroup())
        .childHandler(new ChannelInitializer() {

            @Override
            protected void initChannel(Channel ch) throws Exception {
                ch.pipeline()
                    .addLast(new ChannelInboundHandlerAdapter() {

                        @Override
                        public void exceptionCaught(ChannelHandlerContext ctx, Throwable cause) throws Exception {
                            System.out.println(cause.getMessage());
                        }
                    });
            }
        });

    Channel channel = serverBootstrap.bind(8080).awaitUninterruptibly().channel();
    channel.closeFuture().awaitUninterruptibly();
}

}

Netty version

4.1.33

JVM version (e.g. java -version)

java version “1.8.0_181” Java™ SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot™ 64-Bit Server VM (build 25.181-b13, mixed mode)

OS version (e.g. uname -a)

18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64 x86_64

[normanmaurer]

@kachayev ups yes… let me remove.

[amizurov]

@normanmaurer Thanks, looks good. No more WARN messages on my side.