StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POworker thread being blocked in Netty
text
Body
copied!<p>I know netty uses the Reactor pattern <strong>to avoid creating a thread for each connection</strong>, the core concept about this pattern is a "selector" or <code>epoll</code> system call in Linux. </p> <p>But I also heard about that if a handler never close it's channel, it will occupy one worker thread and block it: doesn't that mean each connetion will use (block) one thread,so <strong>for each accepted socket we still need to create a thread ?</strong></p> <p>for example ,if I write a server with 10,000 persistent connections,does this server need 10,000 worker threads??</p> <p>The contradiction between those two things above confused me ,can anyone explain me if I understand it wrong? thank you~ </p> <p>========================================</p> <p>an example (with only 1 worker thread ) which can always process one client's event in the same time. </p> <pre><code>import java.net.InetSocketAddress; import java.util.concurrent.Executors; import org.jboss.netty.bootstrap.ServerBootstrap; import org.jboss.netty.buffer.ChannelBuffer; import org.jboss.netty.channel.*; import org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory; public class Netty_test { public static void main(String[] args) { ChannelFactory factory =new NioServerSocketChannelFactory(Executors.newCachedThreadPool(),Executors.newFixedThreadPool(1)); ServerBootstrap bootstrap = new ServerBootstrap(factory); ChannelPipelineFactory cpf=new ChannelPipelineFactory(){ public ChannelPipeline getPipeline() { return Channels.pipeline(new testHandler()); } }; bootstrap.setPipelineFactory(cpf); bootstrap.setOption("child.tcpNoDelay", true); bootstrap.bind(new InetSocketAddress(100)); } } class testHandler extends SimpleChannelHandler { @Override public void messageReceived(ChannelHandlerContext ctx, MessageEvent e) { System.out.println("messageReceived, handler work."); e.getChannel().write(e.getMessage()); ctx.sendUpstream(e); } } </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload