本节主要分析server的启动过程。

Netty是基于Nio实现的,所以也离不开selector、serverSocketChannel、socketChannel和selectKey等,只不过Netty把这些实现都封装在了底层。

从示例可以看出,一切从ServerBootstrap开始。

ServerBootstrap实例中需要两个NioEventLoopGroup实例,分别为boss和work,有不同的分工:
1、 boss负责请求的accept操作。
2、 work负责请求的read、write和处理操作。

NioEventLoopGroup

NioEventLoopGroup主要负责管理eventLoop的生命周期,eventLoop数量默认为处理器个数的两倍。

NioEventLoopGroup

继承关系如下:

NioEventLoopGroup

NioEventLoopGroup构造方法:

  1. public NioEventLoopGroup() {
  2. this(0);
  3. }
  4.  
  5. public NioEventLoopGroup(int nThreads) {
  6. this(nThreads, null);
  7. }
  8.  
  9. public NioEventLoopGroup(int nThreads, ThreadFactory threadFactory) {
  10. this(nThreads, threadFactory, SelectorProvider.provider());
  11. }
  12.  
  13. public NioEventLoopGroup(
  14. int nThreads, ThreadFactory threadFactory, final SelectorProvider selectorProvider) {
  15. super(nThreads, threadFactory, selectorProvider);
  16. }

MultithreadEventLoopGroup构造方法:

  1. protected MultithreadEventLoopGroup(int nThreads, ThreadFactory threadFactory, Object... args) {
  2. super(nThreads == 0? DEFAULT_EVENT_LOOP_THREADS : nThreads, threadFactory, args);
  3. }
  1. 其中 DEFAULT_EVENT_LOOP_THREADS 为处理器数量的两倍。

MultithreadEventExecutorGroup是核心,管理eventLoop的生命周期,先看看其中几个变量。
1、children:EventExecutor数组,保存eventLoop。
2、chooser:从children中选取一个eventLoop的策略。

构造方法:

  1. protected MultithreadEventExecutorGroup(int nThreads, ThreadFactory threadFactory, Object... args) {
  2. if (nThreads <= 0) {
  3. throw new IllegalArgumentException(String.format("nThreads: %d (expected: > 0)", nThreads));
  4. }
  5.  
  6. if (threadFactory == null) {
  7. threadFactory = newDefaultThreadFactory();
  8. }
  9.  
  10. children = new SingleThreadEventExecutor[nThreads];
  11. if (isPowerOfTwo(children.length)) {
  12. chooser = new PowerOfTwoEventExecutorChooser();
  13. } else {
  14. chooser = new GenericEventExecutorChooser();
  15. }
  16.  
  17. for (int i = 0; i < nThreads; i ++) {
  18. boolean success = false;
  19. try {
  20. children[i] = newChild(threadFactory, args);
  21. success = true;
  22. } catch (Exception e) {
  23. // TODO: Think about if this is a good exception type
  24. throw new IllegalStateException("failed to create a child event loop", e);
  25. } finally {
  26. if (!success) {
  27. for (int j = 0; j < i; j ++) {
  28. children[j].shutdownGracefully();
  29. }
  30.  
  31. for (int j = 0; j < i; j ++) {
  32. EventExecutor e = children[j];
  33. try {
  34. while (!e.isTerminated()) {
  35. e.awaitTermination(Integer.MAX_VALUE, TimeUnit.SECONDS);
  36. }
  37. } catch (InterruptedException interrupted) {
  38. Thread.currentThread().interrupt();
  39. break;
  40. }
  41. }
  42. }
  43. }
  44. }
  45.  
  46. final FutureListener<Object> terminationListener = new FutureListener<Object>() {
  47. @Override
  48. public void operationComplete(Future<Object> future) throws Exception {
  49. if (terminatedChildren.incrementAndGet() == children.length) {
  50. terminationFuture.setSuccess(null);
  51. }
  52. }
  53. };
  54.  
  55. for (EventExecutor e: children) {
  56. e.terminationFuture().addListener(terminationListener);
  57. }
  58. }
  59.  
  60. protected EventExecutor newChild(
  61. ThreadFactory threadFactory, Object... args) throws Exception {
  62. return new NioEventLoop(this, threadFactory, (SelectorProvider) args[0]);
  63. }

1、 根据数组的大小,采用不同策略初始化chooser。
如果大小为2的幂次方,则采用PowerOfTwoEventExecutorChooser;否则使用GenericEventExecutorChooser。
判断一个数是否是2的幂次方的方法,觉得很赞。

  1. private static boolean isPowerOfTwo(int val) {
  2. return (val & -val) == val;
  3. }

2、newChild方法重载,初始化EventExecutor时,实际执行的是NioEventLoopGroup中的newChild方法,所以,children元素的实际类型为NioEventLoop。


接下去看看NioEventLoop类。

NioEventLoop

每个eventLoop会维护一个selector和taskQueue,负责处理客户端请求和内部任务,如ServerSocketChannel注册和ServerSocket绑定等。

NioEventLoop

继承关系如下:

NioEventLoop

构造方法:

  1. NioEventLoop(NioEventLoopGroup parent, ThreadFactory threadFactory, SelectorProvider selectorProvider) {
  2. super(parent, threadFactory, false);
  3. if (selectorProvider == null) {
  4. throw new NullPointerException("selectorProvider");
  5. }
  6. provider = selectorProvider;
  7. selector = openSelector();
  8. }

当看到 selector = openSelector() 时,有没有觉得亲切了许多,这里先不管 selector,看看SingleThreadEventLoop类。

SingleThreadEventLoop 构造方法:

  1. protected SingleThreadEventLoop(EventLoopGroup parent, ThreadFactory threadFactory, boolean addTaskWakesUp) {
  2. super(parent, threadFactory, addTaskWakesUp);
  3. }

啥事都没做...


SingleThreadEventExecutor
从命名上可以看出,这是一个只有一个线程的线程池, 先看看其中的几个变量:
1、state:线程池当前的状态
2、taskQueue:存放任务的队列
3、thread:线程池维护的唯一线程
4、scheduledTaskQueue:定义在其父类AbstractScheduledEventExecutor中,用以保存延迟执行的任务。
...
构造方法:

  1. protected SingleThreadEventExecutor(EventExecutorGroup parent, ThreadFactory threadFactory, boolean addTaskWakesUp) {
  2. if (threadFactory == null) {
  3. throw new NullPointerException("threadFactory");
  4. }
  5. this.parent = parent;
  6. this.addTaskWakesUp = addTaskWakesUp;
  7.  
  8. thread = threadFactory.newThread(new Runnable() {
  9. @Override
  10. public void run() {
  11. boolean success = false;
  12. updateLastExecutionTime();
  13. try {
  14. SingleThreadEventExecutor.this.run();
  15. success = true;
  16. } catch (Throwable t) {
  17. logger.warn("Unexpected exception from an event executor: ", t);
  18. } finally {
  19. for (;;) {
  20. int oldState = STATE_UPDATER.get(SingleThreadEventExecutor.this);
  21. if (oldState >= ST_SHUTTING_DOWN || STATE_UPDATER.compareAndSet(
  22. SingleThreadEventExecutor.this, oldState, ST_SHUTTING_DOWN)) {
  23. break;
  24. }
  25. }
  26. // Check if confirmShutdown() was called at the end of the loop.
  27. if (success && gracefulShutdownStartTime == 0) {
  28. logger.error(
  29. "Buggy " + EventExecutor.class.getSimpleName() + " implementation; " +
  30. SingleThreadEventExecutor.class.getSimpleName() + ".confirmShutdown() must be called " +
  31. "before run() implementation terminates.");
  32. }
  33.  
  34. try {
  35. // Run all remaining tasks and shutdown hooks.
  36. for (;;) {
  37. if (confirmShutdown()) {
  38. break;
  39. }
  40. }
  41. } finally {
  42. try {
  43. cleanup();
  44. } finally {
  45. STATE_UPDATER.set(SingleThreadEventExecutor.this, ST_TERMINATED);
  46. threadLock.release();
  47. if (!taskQueue.isEmpty()) {
  48. logger.warn(
  49. "An event executor terminated with " +
  50. "non-empty task queue (" + taskQueue.size() + ')');
  51. }
  52.  
  53. terminationFuture.setSuccess(null);
  54. }
  55. }
  56. }
  57. }
  58. });
  59. threadProperties = new DefaultThreadProperties(thread);
  60. taskQueue = newTaskQueue();
  61. }

代码很长,内容很简单:
1、初始化一个线程,并在线程内部执行NioEventLoop类的run方法,当然这个线程不会立刻执行。
2、使用LinkedBlockingQueue类初始化taskQueue。

ServerBootstrap

通过serverBootstrap.bind(port)启动服务,过程如下:

bind过程

doBind实现如下

  1. private ChannelFuture doBind(final SocketAddress localAddress) {
  2. final ChannelFuture regFuture = initAndRegister();
  3. final Channel channel = regFuture.channel();
  4. if (regFuture.cause() != null) {
  5. return regFuture;
  6. }
  7.  
  8. if (regFuture.isDone()) {
  9. // At this point we know that the registration was complete and successful.
  10. ChannelPromise promise = channel.newPromise();
  11. doBind0(regFuture, channel, localAddress, promise);
  12. return promise;
  13. } else {
  14. // Registration future is almost always fulfilled already, but just in case it's not.
  15. final PendingRegistrationPromise promise = new PendingRegistrationPromise(channel);
  16. regFuture.addListener(new ChannelFutureListener() {
  17. @Override
  18. public void operationComplete(ChannelFuture future) throws Exception {
  19. Throwable cause = future.cause();
  20. if (cause != null) {
  21. // Registration on the EventLoop failed so fail the ChannelPromise directly to not cause an
  22. // IllegalStateException once we try to access the EventLoop of the Channel.
  23. promise.setFailure(cause);
  24. } else {
  25. // Registration was successful, so set the correct executor to use.
  26. // See https://github.com/netty/netty/issues/2586
  27. promise.executor = channel.eventLoop();
  28. }
  29. doBind0(regFuture, channel, localAddress, promise);
  30. }
  31. });
  32. return promise;
  33. }
  34. }

1、方法initAndRegister返回一个ChannelFuture实例regFuture,通过regFuture可以判断initAndRegister执行结果。
2、如果regFuture.isDone()为true,说明initAndRegister已经执行完,则直接执行doBind0进行socket绑定。
3、否则regFuture添加一个ChannelFutureListener监听,当initAndRegister执行完成时,调用operationComplete方法并执行doBind0进行socket绑定。

所以只有当initAndRegister操作结束之后才能进行bind操作。

initAndRegister

  1. final ChannelFuture initAndRegister() {
  2. final Channel channel = channelFactory().newChannel();
  3. try {
  4. init(channel);
  5. } catch (Throwable t) {
  6. channel.unsafe().closeForcibly();
  7. // as the Channel is not registered yet we need to force the usage of the GlobalEventExecutor
  8. return new DefaultChannelPromise(channel, GlobalEventExecutor.INSTANCE).setFailure(t);
  9. }
  10.  
  11. ChannelFuture regFuture = group().register(channel);
  12. if (regFuture.cause() != null) {
  13. if (channel.isRegistered()) {
  14. channel.close();
  15. } else {
  16. channel.unsafe().closeForcibly();
  17. }
  18. }
  19. return regFuture;
  20. }

1、主要负责创建服务端channel,在本例子中,创建了NioServerSocketChannel。
2、为NioServerSocketChannel的pipeline添加handler。
3、注册NioServerSocketChannel到selector。

NioServerSocketChannel

对Nio的ServerSocketChannel和SelectionKey进行了封装。

继承关系:

NioServerSocketChannel继承关系

构造方法:

  1. public NioServerSocketChannel() {
  2. this(newSocket(DEFAULT_SELECTOR_PROVIDER));
  3. }
  4.  
  5. private static ServerSocketChannel newSocket(SelectorProvider provider) {
  6. try {
  7. return provider.openServerSocketChannel();
  8. } catch (IOException e) {
  9. throw new ChannelException(
  10. "Failed to open a server socket.", e);
  11. }
  12. }
  1. public NioServerSocketChannel(ServerSocketChannel channel) {
  2. super(null, channel, SelectionKey.OP_ACCEPT);
  3. config = new NioServerSocketChannelConfig(this, javaChannel().socket());
  4. }

1、方法newSocket利用 provider.openServerSocketChannel() 生成Nio中的ServerSocketChannel对象。
2、设置SelectionKey.OP_ACCEPT事件。

AbstractNioMessageChannel构造方法

  1. protected AbstractNioMessageChannel(Channel parent, SelectableChannel ch, int readInterestOp) {
  2. super(parent, ch, readInterestOp);
  3. }

啥也没做...

AbstractNioChannel构造方法

  1. protected AbstractNioChannel(Channel parent, SelectableChannel ch, int readInterestOp) {
  2. super(parent);
  3. this.ch = ch;
  4. this.readInterestOp = readInterestOp;
  5. try {
  6. ch.configureBlocking(false);
  7. } catch (IOException e) {
  8. try {
  9. ch.close();
  10. } catch (IOException e2) {
  11. if (logger.isWarnEnabled()) {
  12. logger.warn(
  13. "Failed to close a partially initialized socket.", e2);
  14. }
  15. }
  16.  
  17. throw new ChannelException("Failed to enter non-blocking mode.", e);
  18. }
  19. }

设置当前ServerSocketChannel为非阻塞通道。

AbstractChannel构造方法

  1. protected AbstractChannel(Channel parent) {
  2. this.parent = parent;
  3. unsafe = newUnsafe();
  4. pipeline = new DefaultChannelPipeline(this);
  5. }

1、初始化unsafe。
这里的Unsafe并非是jdk中底层Unsafe类,用来负责底层的connect、register、read和write等操作。

2、初始化pipeline。
每个Channel都有自己的pipeline,当有请求事件发生时,pipeline负责调用相应的hander进行处理。

unsafe和pipeline的具体实现原理会在后续进行分析。


回到ServerBootstrap的init(Channel channel)方法,添加handler到channel的pipeline中。

  1. void init(Channel channel) throws Exception {
  2. final Map<ChannelOption<?>, Object> options = options();
  3. synchronized (options) {
  4. channel.config().setOptions(options);
  5. }
  6.  
  7. final Map<AttributeKey<?>, Object> attrs = attrs();
  8. synchronized (attrs) {
  9. for (Entry<AttributeKey<?>, Object> e: attrs.entrySet()) {
  10. @SuppressWarnings("unchecked")
  11. AttributeKey<Object> key = (AttributeKey<Object>) e.getKey();
  12. channel.attr(key).set(e.getValue());
  13. }
  14. }
  15.  
  16. ChannelPipeline p = channel.pipeline();
  17.  
  18. final EventLoopGroup currentChildGroup = childGroup;
  19. final ChannelHandler currentChildHandler = childHandler;
  20. final Entry<ChannelOption<?>, Object>[] currentChildOptions;
  21. final Entry<AttributeKey<?>, Object>[] currentChildAttrs;
  22. synchronized (childOptions) {
  23. currentChildOptions = childOptions.entrySet().toArray(newOptionArray(childOptions.size()));
  24. }
  25. synchronized (childAttrs) {
  26. currentChildAttrs = childAttrs.entrySet().toArray(newAttrArray(childAttrs.size()));
  27. }
  28.  
  29. p.addLast(new ChannelInitializer<Channel>() {
  30. @Override
  31. public void initChannel(Channel ch) throws Exception {
  32. ChannelPipeline pipeline = ch.pipeline();
  33. ChannelHandler handler = handler();
  34. if (handler != null) {
  35. pipeline.addLast(handler);
  36. }
  37. pipeline.addLast(new ServerBootstrapAcceptor(
  38. currentChildGroup, currentChildHandler, currentChildOptions, currentChildAttrs));
  39. }
  40. });
  41. }

1、设置channel的options和attrs。
2、在pipeline中添加一个ChannelInitializer对象。


init执行完,需要把当前channel注册到EventLoopGroup。
其实最终目的是为了实现Nio中把ServerSocket注册到selector上,这样就可以实现client请求的监听了。
看看Netty中是如何实现的:

  1. public ChannelFuture register(Channel channel, ChannelPromise promise) {
  2. return next().register(channel, promise);
  3. }
  4.  
  5. public EventLoop next() {
  6. return (EventLoop) super.next();
  7. }
  8.  
  9. public EventExecutor next() {
  10. return children[Math.abs(childIndex.getAndIncrement() % children.length)];
  11. }

因为EventLoopGroup中维护了多个eventLoop,next方法会调用chooser策略找到下一个eventLoop,并执行eventLoop的register方法进行注册。

  1. public ChannelFuture register(final Channel channel, final ChannelPromise promise) {
  2. ...
  3. channel.unsafe().register(this, promise);
  4. return promise;
  5. }

channel.unsafe()是什么?
NioServerSocketChannel初始化时,会创建一个NioMessageUnsafe实例,用于实现底层的register、read、write等操作。

  1. eventLoop.execute(new Runnable() {
  2. @Override
  3. public void run() {
  4. register0(promise);
  5. }
  6. });
  7.  
  8. private void register0(ChannelPromise promise) {
  9. try {
  10. if (!ensureOpen(promise)) {
  11. return;
  12. }
  13. Runnable postRegisterTask = doRegister();
  14. registered = true;
  15. promise.setSuccess();
  16. pipeline.fireChannelRegistered();
  17. if (postRegisterTask != null) {
  18. postRegisterTask.run();
  19. }
  20. if (isActive()) {
  21. pipeline.fireChannelActive();
  22. }
  23. } catch (Throwable t) {
  24. // Close the channel directly to avoid FD leak.
  25. closeForcibly();
  26. if (!promise.tryFailure(t)) {
  27.  
  28. }
  29. closeFuture.setClosed();
  30. }
  31. }
  32.  
  33. public void execute(Runnable task) {
  34. if (task == null) {
  35. throw new NullPointerException("task");
  36. }
  37.  
  38. boolean inEventLoop = inEventLoop();
  39. if (inEventLoop) {
  40. addTask(task);
  41. } else {
  42. startThread();
  43. addTask(task);
  44. if (isShutdown() && removeTask(task)) {
  45. reject();
  46. }
  47. }
  48.  
  49. if (!addTaskWakesUp) {
  50. wakeup(inEventLoop);
  51. }
  52. }

1、register0方法提交到eventLoop线程池中执行,这个时候会启动eventLoop中的线程。
2、方法doRegister()才是最终Nio中的注册方法,方法javaChannel()获取ServerSocketChannel。

  1. protected Runnable doRegister() throws Exception {
  2. boolean selected = false;
  3. for (;;) {
  4. try {
  5. selectionKey = javaChannel().register(eventLoop().selector, 0, this);
  6. return null;
  7. } catch (CancelledKeyException e) {
  8. if (!selected) {
  9. // Force the Selector to select now as the "canceled" SelectionKey may still be
  10. // cached and not removed because no Select.select(..) operation was called yet.
  11. eventLoop().selectNow();
  12. selected = true;
  13. } else {
  14. // We forced a select operation on the selector before but the SelectionKey is still cached
  15. // for whatever reason. JDK bug ?
  16. throw e;
  17. }
  18. }
  19. }
  20. }

ServerSocketChannel注册完之后,通知pipeline执行fireChannelRegistered方法,pipeline中维护了handler链表,通过遍历链表,执行InBound类型handler的channelRegistered方法,最终执行init中添加的ChannelInitializer handler。

  1. public final void channelRegistered(ChannelHandlerContext ctx)
  2. throws Exception {
  3. boolean removed = false;
  4. boolean success = false;
  5. try {
  6. initChannel((C) ctx.channel());
  7. ctx.pipeline().remove(this);
  8. removed = true;
  9. ctx.fireChannelRegistered();
  10. success = true;
  11. } catch (Throwable t) {
  12. logger.warn("Failed to initialize a channel. Closing: " + ctx.channel(), t);
  13. } finally {
  14. if (!removed) {
  15. ctx.pipeline().remove(this);
  16. }
  17. if (!success) {
  18. ctx.close();
  19. }
  20. }
  21. }

1、initChannel方法最终把ServerBootstrapAcceptor添加到ServerSocketChannel的pipeline,负责accept客户端请求。
2、在pipeline中删除对应的handler。
3、触发fireChannelRegistered方法,可以自定义handler的channelRegistered方法。

到目前为止,ServerSocketChannel完成了初始化并注册到seletor上,启动线程执行selector.select()方法准备接受客户端请求。

细心的同学已经发现,ServerSocketChannel的socket还未绑定到指定端口,那么这一块Netty是如何实现的?
Netty把注册操作放到eventLoop中执行。

  1. private static void doBind0(
  2. final ChannelFuture regFuture,
  3. final Channel channel,
  4. final SocketAddress localAddress,
  5. final ChannelPromise promise) {
  6. channel.eventLoop().execute(new Runnable() {
  7. @Override
  8. public void run() {
  9. if (regFuture.isSuccess()) {
  10. channel.bind(localAddress, promise)
  11. .addListener(ChannelFutureListener.CLOSE_ON_FAILURE);
  12. } else {
  13. promise.setFailure(regFuture.cause());
  14. }
  15. }
  16. });
  17. }
  18.  
  19. public ChannelFuture bind(SocketAddress localAddress, ChannelPromise promise) {
  20. return pipeline.bind(localAddress, promise);
  21. }
  22.  
  23. @Override
  24. public ChannelFuture bind(SocketAddress localAddress, ChannelPromise promise) {
  25. return tail.bind(localAddress, promise);
  26. }
  27.  
  28. @Override
  29. public ChannelFuture bind(SocketAddress localAddress, ChannelPromise promise) {
  30. if (localAddress == null) {
  31. throw new NullPointerException("localAddress");
  32. }
  33. validatePromise(promise, false);
  34. return findContextOutbound().invokeBind(localAddress, promise);
  35. }
  36.  
  37. private ChannelFuture invokeBind(final SocketAddress localAddress, final ChannelPromise promise) {
  38. EventExecutor executor = executor();
  39. if (executor.inEventLoop()) {
  40. invokeBind0(localAddress, promise);
  41. } else {
  42. executor.execute(new Runnable() {
  43. @Override
  44. public void run() {
  45. invokeBind0(localAddress, promise);
  46. }
  47. });
  48. }
  49. return promise;
  50. }
  51.  
  52. private void invokeBind0(SocketAddress localAddress, ChannelPromise promise) {
  53. try {
  54. ((ChannelOutboundHandler) handler()).bind(this, localAddress, promise);
  55. } catch (Throwable t) {
  56. notifyOutboundHandlerException(t, promise);
  57. }
  58. }
  59.  
  60. @Override
  61. public void bind(
  62. ChannelHandlerContext ctx, SocketAddress localAddress, ChannelPromise promise)
  63. throws Exception {
  64. unsafe.bind(localAddress, promise);
  65. }

最终由unsafe实现端口的bind操作。

  1. public final void bind(final SocketAddress localAddress, final ChannelPromise promise) {
  2. if (!ensureOpen(promise)) {
  3. return;
  4. }
  5.  
  6. try {
  7. boolean wasActive = isActive();
  8. ...
  9. doBind(localAddress);
  10. promise.setSuccess();
  11. if (!wasActive && isActive()) {
  12. pipeline.fireChannelActive();
  13. }
  14. } catch (Throwable t) {
  15. promise.setFailure(t);
  16. closeIfClosed();
  17. }
  18. }
  19.  
  20. protected void doBind(SocketAddress localAddress) throws Exception {
  21. javaChannel().socket().bind(localAddress, config.getBacklog());
  22. }

bind完成后,且ServerSocketChannel也已经注册完成,则触发pipeline的fireChannelActive方法,所以在这里可以自定义fireChannelActive方法,默认执行tail的fireChannelActive。

  1. @Override
  2. public ChannelPipeline fireChannelActive() {
  3. head.fireChannelActive();
  4.  
  5. if (channel.config().isAutoRead()) {
  6. channel.read();
  7. }
  8.  
  9. return this;
  10. }

channel.read()方法会触发pipeline的行为:

  1. @Override
  2. public Channel read() {
  3. pipeline.read();
  4. return this;
  5. }
  6.  
  7. @Override
  8. public ChannelPipeline read() {
  9. tail.read();
  10. return this;
  11. }
  12.  
  13. @Override
  14. public ChannelHandlerContext read() {
  15. findContextOutbound().invokeRead();
  16. return this;
  17. }
  18.  
  19. private void invokeRead() {
  20. EventExecutor executor = executor();
  21. if (executor.inEventLoop()) {
  22. invokeRead0();
  23. } else {
  24. Runnable task = invokeRead0Task;
  25. if (task == null) {
  26. invokeRead0Task = task = new Runnable() {
  27. @Override
  28. public void run() {
  29. invokeRead0();
  30. }
  31. };
  32. }
  33. executor.execute(task);
  34. }
  35. }
  36.  
  37. private void invokeRead0() {
  38. try {
  39. ((ChannelOutboundHandler) handler()).read(this);
  40. } catch (Throwable t) {
  41. notifyHandlerException(t);
  42. }
  43. }

最终会在pipeline中找到handler执行read方法,默认是head。

至此为止,server已经启动完成。

Netty源码分析之服务启动的更多相关文章

  1. Netty源码分析之服务端启动过程

    一.首先来看一段服务端的示例代码: public class NettyTestServer { public void bind(int port) throws Exception{ EventL ...

  2. Netty源码分析之客户端启动过程

    一.先来看一下客户端示例代码. public class NettyClientTest { public void connect(int port, String host) throws Exc ...

  3. Netty源码分析之服务端启动

    Netty服务端启动代码: public final class EchoServer { static final int PORT = Integer.parseInt(System.getPro ...

  4. Netty源码分析第1章(Netty启动流程)---->第1节: 服务端初始化

    Netty源码分析第一章:  Server启动流程 概述: 本章主要讲解server启动的关键步骤, 读者只需要了解server启动的大概逻辑, 知道关键的步骤在哪个类执行即可, 并不需要了解每一步的 ...

  5. Netty源码分析第1章(Netty启动流程)---->第3节: 服务端channel初始化

    Netty源码分析第一章:Netty启动流程   第三节:服务端channel初始化 回顾上一小节的initAndRegister()方法: final ChannelFuture initAndRe ...

  6. Netty源码分析 (三)----- 服务端启动源码分析

    本文接着前两篇文章来讲,主要讲服务端类剩下的部分,我们还是来先看看服务端的代码 /** * Created by chenhao on 2019/9/4. */ public final class ...

  7. Netty源码分析第1章(Netty启动流程)---->第2节: NioServerSocketChannel的创建

    Netty源码分析第一章:  Server启动流程 第二节:NioServerSocketChannel的创建 我们如果熟悉Nio, 则对channel的概念则不会陌生, channel在相当于一个通 ...

  8. Netty源码分析第1章(Netty启动流程)---->第4节: 注册多路复用

    Netty源码分析第一章:Netty启动流程   第四节:注册多路复用 回顾下以上的小节, 我们知道了channel的的创建和初始化过程, 那么channel是如何注册到selector中的呢?我们继 ...

  9. 【Netty源码分析】客户端connect服务端过程

    上一篇博客[Netty源码分析]Netty服务端bind端口过程 我们介绍了服务端绑定端口的过程,这一篇博客我们介绍一下客户端连接服务端的过程. ChannelFuture future = boos ...

随机推荐

  1. predict predict_proba区别的小例子

    predict_proba返回的是一个n行k列的数组,第i行第j列上的数值是模型预测第i个预测样本的标签为j的概率.所以每一行的和应该等于1. 举个例子 >>> from sklea ...

  2. boost asio 学习(三)post与dispatch

    http://www.gamedev.net/blog/950/entry-2249317-a-guide-to-getting-started-with-boostasio?pg=4 本章节为io_ ...

  3. .net 简单任务调度平台安装简要说明

    .net 简单任务调度平台,用于.net dll,exe的任务的挂载,任务的隔离,调度执行,访问权限控制,监控,管理,日志,错误预警,性能分析等. 平台基于quartz.net进行任务调度功能开发,采 ...

  4. ES6最新语法

    ECMAScript 6(以下简称ES6)是JavaScript语言的下一代标准.因为当前版本的ES6是在2015年发布的,所以又称ECMAScript 2015. 也就是说,ES6就是ES2015. ...

  5. Knockout.js组件系统的详解之(一) - 组件的定义和注册

    (Knockout版本:3.4.1 ) KO的组件主要从以下四个部分进行详细介绍: 1.组件的定义和注册 2.组件绑定 3.使用自定义元素 4.自定义组件加载器(高级) 目录结构 1.通过" ...

  6. SIFT算法

     备注:源代码还未理解,所以未附上——下周任务 一.SIFT算法 1.算法简介 尺度不变特征转换即SIFT (Scale-invariant feature transform)是一种计算机视觉的算法 ...

  7. # 2019-2020-3 《Java 程序设计》第五周学习总结

    2019-2020-3 <Java 程序设计>第五周知识总结 1.使用interface来定义一个接口.接口定义同类的定义类似,也是分为接口的声明和接口体,其中接口体由常量定义和方法定义两 ...

  8. 第一个SpringBoot应用

    第一个SpringBoot应用 新建eclipse项目 编写pom文件,配置maven导入的springboot的jar包 <?xml version="1.0" encod ...

  9. AJAX笔记整理

    AJAX: Asynchronous JavaScript and XML,异步的Javascirpt和Xml. Asynchronous:异步 与之对应的是 synchronous:同步,我们要知道 ...

  10. 第三周Access的总结

    一.问;这节课你学到了什么知识? 答:这周我学得比较少,主要是学Access的数据库进行基本的维护. 2.3数据库的基本维护 对Access定期检查,修复是整个数据库重要部分: 1.Access可修复 ...