How Netty Accepts Connections: Inside NioEventLoop and Worker Threads

Boss Thread – Accepting Connections

The boss NioEventLoop continuously polls its selector for OP_ACCEPT events. When a new client connects, the selector reports the event, and the server creates a SocketChannel via serverSocketChannel.accept(). The channel is then registered with the selector using

selectionKey = javaChannel().register(eventLoop().unwrappedSelector(), 0, this)

, initially with interest ops set to 0.

Worker Thread – Registering for Read

The selected SocketChannel is handed off to a worker NioEventLoop. The worker registers the channel for read events ( OP_READ) on its selector, enabling the server to receive data from the client. This registration is performed in the ServerBootstrapAcceptor via pipeline.fireChannelRead and later triggers fireChannelActive (implemented in AbstractChannel.AbstractUnsafe#register0).

During the first registration, the interest ops are 0 rather than OP_READ; the actual read interest is set after the channel becomes active.

// Blocking, non‑blocking, and timed selector polling
selector.select() / selectNow() / select(timeoutMillis) // detects OP_ACCEPT
SocketChannel socketChannel = serverSocketChannel.accept();
selectionKey = javaChannel().register(eventLoop().unwrappedSelector(), 0, this);
selectionKey.interestOps(OP_READ);

After registration, the worker’s NioEventLoop starts handling read operations. Netty does not repeatedly attempt reads (e.g., 16 times) because it cannot know if more connections will arrive, so it processes each ready read event once.

Overall, the connection acceptance flow consists of the boss thread detecting OP_ACCEPT, creating and registering the channel, and the worker thread finalizing the registration to listen for OP_READ, after which data can be read from the client.