Examples of NioClientSocketChannelFactory

com.facebook.presto.jdbc.internal.netty.channel.socket.nio.NioClientSocketChannelFactory
A {@link ClientSocketChannelFactory} which creates a client-side NIO-based{@link SocketChannel}. It utilizes the non-blocking I/O mode which was introduced with NIO to serve many number of concurrent connections efficiently.
How threads work

There are two types of threads in a {@link NioClientSocketChannelFactory}; one is boss thread and the other is worker thread.
Boss thread

One {@link NioClientSocketChannelFactory} has one boss thread. It makesa connection attempt on request. Once a connection attempt succeeds, the boss thread passes the connected {@link Channel} to one of the workerthreads that the {@link NioClientSocketChannelFactory} manages.
Worker threads

One {@link NioClientSocketChannelFactory} can have one or more workerthreads. A worker thread performs non-blocking read and write for one or more {@link Channel}s in a non-blocking mode.
Life cycle of threads and graceful shutdown

All threads are acquired from the {@link Executor}s which were specified when a {@link NioClientSocketChannelFactory} 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 Executor}s are able to lend the sufficient number of threads. It is the best bet to specify {@linkplain 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 Selector} are also released when the boss and worker threads arereleased. Therefore, to shut down a service gracefully, you should do the following:
1. close all channels created by the factory usually using {@link ChannelGroup#close()}, and
2. call {@link #releaseExternalResources()}.
Please make sure not to shut down the executor until all channels are closed. Otherwise, you will end up with a {@link RejectedExecutionException}and the related resources might not be released properly. @apiviz.landmark
io.netty.channel.socket.nio.NioClientSocketChannelFactory
A {@link ClientSocketChannelFactory} which creates a client-side NIO-based{@link SocketChannel}. It utilizes the non-blocking I/O mode which was introduced with NIO to serve many number of concurrent connections efficiently.
How threads work

There are two types of threads in a {@link NioClientSocketChannelFactory}; one is boss thread and the other is worker thread.
Boss thread

One {@link NioClientSocketChannelFactory} has one boss thread. It makesa connection attempt on request. Once a connection attempt succeeds, the boss thread passes the connected {@link Channel} to one of the workerthreads that the {@link NioClientSocketChannelFactory} manages.
Worker threads

One {@link NioClientSocketChannelFactory} can have one or more workerthreads. A worker thread performs non-blocking read and write for one or more {@link Channel}s in a non-blocking mode.
Life cycle of threads and graceful shutdown

All threads are acquired from the {@link Executor}s which were specified when a {@link NioClientSocketChannelFactory} 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 Executor}s are able to lend the sufficient number of threads. It is the best bet to specify {@linkplain 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 Selector} are also released when the boss and worker threads arereleased. Therefore, to shut down a service gracefully, you should do the following:
1. close all channels created by the factory usually using {@link ChannelGroup#close()}, and
2. call {@link #releaseExternalResources()}.
Please make sure not to shut down the executor until all channels are closed. Otherwise, you will end up with a {@link RejectedExecutionException}and the related resources might not be released properly. @apiviz.landmark
org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketChannelFactory
org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory
A {@link ClientSocketChannelFactory} which creates a client-side NIO-based{@link SocketChannel}. It utilizes the non-blocking I/O mode which was introduced with NIO to serve many number of concurrent connections efficiently.
How threads work

There are two types of threads in a {@link NioClientSocketChannelFactory}; one is boss thread and the other is worker thread.
Boss thread

One {@link NioClientSocketChannelFactory} has one boss thread. It makesa connection attempt on request. Once a connection attempt succeeds, the boss thread passes the connected {@link Channel} to one of the workerthreads that the {@link NioClientSocketChannelFactory} manages.
Worker threads

One {@link NioClientSocketChannelFactory} can have one or more workerthreads. A worker thread performs non-blocking read and write for one or more {@link Channel}s in a non-blocking mode.
Life cycle of threads and graceful shutdown

All threads are acquired from the {@link Executor}s which were specified when a {@link NioClientSocketChannelFactory} 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 Executor}s are able to lend the sufficient number of threads. It is the best bet to specify {@linkplain 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 Selector} are also released when the boss and worker threads arereleased. Therefore, to shut down a service gracefully, you should do the following:
1. close all channels created by the factory, and
2. call {@link #releaseExternalResources()}.
Please make sure not to shut down the executor until all channels are closed. Otherwise, you will end up with a {@link RejectedExecutionException}and the related resources might not be released properly. @author The Netty Project (netty-dev@lists.jboss.org) @author Trustin Lee (tlee@redhat.com) @version $Rev: 536 $, $Date: 2008-11-28 20:18:21 +0900 (Fri, 28 Nov 2008) $ @apiviz.landmark

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

            } else if (uri.getScheme().equalsIgnoreCase("https")) {
                port = 443;
            }
        }


        ClientBootstrap clientBootstrap = new ClientBootstrap(new NioClientSocketChannelFactory(
                Executors.newCachedThreadPool(), Executors.newCachedThreadPool()));
        File tmpFile;
        try {
            tmpFile = File.createTempFile("http", "download");
        } catch (IOException e) {

View Full Code Here

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

   * @throws java.io.IOException
   *           if an error occurs connecting to the given address.
   */
  public NettyTransceiver(InetSocketAddress addr, Long connectTimeoutMillis)
      throws IOException {
    this(addr, new NioClientSocketChannelFactory(
        Executors.newCachedThreadPool(new NettyTransceiverThreadFactory("Wasp "
            + NettyTransceiver.class.getSimpleName() + " Boss")),
        Executors.newCachedThreadPool(new NettyTransceiverThreadFactory("Wasp "
            + NettyTransceiver.class.getSimpleName() + " I/O Worker"))),
        connectTimeoutMillis);

View Full Code Here

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory


  static ChannelFuture createChannelFuture(final GenericHttpResponseHandler responseHandler, int port)
  {


    ClientBootstrap client = new ClientBootstrap(
        new NioClientSocketChannelFactory(BOSS_POOL, IO_POOL));
    client.setPipelineFactory(new ChannelPipelineFactory()
    {
      @Override
      public ChannelPipeline getPipeline() throws Exception
      {

View Full Code Here

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

         else
         {
            threadsToUse = this.nioRemotingThreads;
         }


         channelFactory = new NioClientSocketChannelFactory(virtualExecutor, virtualExecutor, threadsToUse);
      }
      else
      {
         channelFactory = new OioClientSocketChannelFactory(virtualExecutor);
      }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of NioClientSocketChannelFactory

How threads work

Boss thread

Worker threads

Life cycle of threads and graceful shutdown

How threads work

Boss thread

Worker threads

Life cycle of threads and graceful shutdown

How threads work

Boss thread

Worker threads

Life cycle of threads and graceful shutdown

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory

Examples of org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory