There are two types of threads in a {@link SctpClientSocketChannelFactory}; one is boss thread and the other is worker thread.
One {@link SctpClientSocketChannelFactory} has one boss thread. It makesa connection attempt on request. Once a connection attempt succeeds, the boss thread passes the connected {@link io.netty.channel.Channel} to one of the workerthreads that the {@link SctpClientSocketChannelFactory} manages.
One {@link SctpClientSocketChannelFactory} can have one or more workerthreads. A worker thread performs non-blocking read and write for one or more {@link io.netty.channel.Channel}s in a non-blocking mode.
All threads are acquired from the {@link java.util.concurrent.Executor}s which were specified when a {@link SctpClientSocketChannelFactory} was created. A boss thread isacquired from the {@code bossExecutor}, and worker threads are acquired from the {@code workerExecutor}. Therefore, you should make sure the specified {@link java.util.concurrent.Executor}s are able to lend the sufficient number of threads. It is the best bet to specify {@linkplain java.util.concurrent.Executors#newCachedThreadPool() a cached thread pool}.
Both boss and worker threads are acquired lazily, and then released when there's nothing left to process. All the related resources such as {@link java.nio.channels.Selector} are also released when the boss and worker threads arereleased. Therefore, to shut down a service gracefully, you should do the following:
|
|