mina 使用线程池例子及socket并发测试

1. 我试了一下2.0M果然可以. 但是服务器端好像不能自己设置连接池了? 下面的代码在2.0不能用,你们怎么用连接池的? 我的性能是要求一台服务器机器需要有1000个并发连接. 我现在服务器这样写不知道有没有问题: 
   

   ExecutorService executor = Executors.newFixedThreadPool(1000);                IoAcceptor acceptor = new NioSocketAcceptor();                acceptor.setHandler(  new TimeServerHandler() );        acceptor.getSessionConfig().setReadBufferSize( 2048 );        acceptor.getSessionConfig().setIdleTime( IdleStatus.BOTH_IDLE, 10 );                acceptor.getFilterChain().addLast("executor",                new ExecutorFilter(executor));        acceptor.getFilterChain().addLast( "logger", new LoggingFilter() );        acceptor.getFilterChain().addLast(                "codec",                new ProtocolCodecFilter( new ObjectSerializationCodecFactory() ) );         acceptor.bind( new InetSocketAddress(PORT) );

   
   
   客户端很简单,就是模拟1000个并发连接: 
   

    public static void main( String[] args ) throws Throwable        {        for(int i=0;i<1000;i++){ log.info("Enter run l..."+i); new Thread(new ClientThread(i)).start(); }        }    

   
   每个客户端代码是: 
   

   public void run() {// TODO Auto-generated method stublog.info("#### thread :"+this.num+" Running...");NioSocketConnector connector = new NioSocketConnector();        // Configure the service.                connector.setConnectTimeoutMillis(CONNECT_TIMEOUT);                       connector.getFilterChain().addLast(                    "codec",                    new ProtocolCodecFilter( new ObjectSerializationCodecFactory() ) );        connector.getFilterChain().addLast( "logger", new LoggingFilter() );        connector.setHandler(new ClientSessionHandler(" hihi new!"));                       IoSession session;        for (;;) {            try {                ConnectFuture future = connector.connect(new InetSocketAddress(                        HOSTNAME, PORT));                future.awaitUninterruptibly();                session = future.getSession();                break;            } catch (Exception e) {                System.err.println("Failed to connect.");                e.printStackTrace();                           }        }        // wait until the summation is done        session.getCloseFuture().awaitUninterruptibly();                connector.dispose();        log.info("#### thread :"+this.num+" over ...");}

   
   不知道这样写是不是已经用了NIO特性和数量是1000的连接池了. 而且我发现客户端如果不用mina的API,直接用Socket API连接,服务器撑不到1000个,200多个就Connection refused了.
   问题补充
   刚才试验了一下,模拟1000个客户端连接,成功了931个,异常是: 
   

   2008-12-28 02:18:06,968 ERROR (LoggingFilter.java:127) - EXCEPTION :java.io.IOException:  您的主机中的软件放弃了一个已建立的连接。at sun.nio.ch.SocketDispatcher.read0(Native Method)at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)at sun.nio.ch.IOUtil.read(IOUtil.java:206)at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:180)at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:42)at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:568)at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:547)at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:539)at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:57)at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:867)at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:65)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)at java.lang.Thread.run(Thread.java:595)

   
   不知道调整哪些参数可以不发生这个错误? 就是说调整什么可以使1000个连接都能连上
   问题补充
   windows需要修改OS的一个设置,但是设置了也不起作用,我再试试吧! java的NIO的目的是使服务器端打开尽量少的Socket连接,能处理尽可能多的客户端请求(不知道主要是非阻塞队列起作用还是那个concurrent线程池在发挥作用,应该是前者),这样理解没错吧?
2. A
   mina 1.1.x版本貌似是 session.close();
   
   对应的方法定义是：   CloseFuture close();
   
   mina 2.0更简单好用。不过我们不是直接用。是参考2.0做了些裁减。
   
   mina的性能没什么可担心的，成功案例有：openfire
   
   可以google一下：openfire connection manager

https://www.ibm.com/developerworks/cn/java/j-lo-mina2/