Return-Path: Delivered-To: apmail-mina-users-archive@www.apache.org Received: (qmail 8345 invoked from network); 28 Mar 2008 05:41:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Mar 2008 05:41:07 -0000 Received: (qmail 53316 invoked by uid 500); 28 Mar 2008 05:41:05 -0000 Delivered-To: apmail-mina-users-archive@mina.apache.org Received: (qmail 53301 invoked by uid 500); 28 Mar 2008 05:41:05 -0000 Mailing-List: contact users-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@mina.apache.org Delivered-To: mailing list users@mina.apache.org Received: (qmail 53291 invoked by uid 99); 28 Mar 2008 05:41:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2008 22:41:05 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trustin@gmail.com designates 209.85.132.245 as permitted sender) Received: from [209.85.132.245] (HELO an-out-0708.google.com) (209.85.132.245) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2008 05:40:23 +0000 Received: by an-out-0708.google.com with SMTP id c2so33571anc.58 for ; Thu, 27 Mar 2008 22:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:subject:from:to:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer; bh=3H/5FN69gjcC1wltBdf1rGU8H3Ge576oBWsew/VZx/4=; b=BxA+YJ9MzicBC5CN2jQbi7lCO/KjVN+2Oxb92NIO/MOYtITSTPWKHGpphaOy79hOY448kRJAQA505iB/Ylos8Il3vvYDTB8xwK8vD1/Zk0Op/qtbQu6Qvbv3KMdI3UwQJwoJj5sJL8XMbaGqNApiHnG9h5NizePy6XHbX+VHUTs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=subject:from:to:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer; b=htEPi6rTDMykYXBFx98xbgyqu2bqQOWl22pkeT8hC9uFKpSTktefvOdaLDNa4qbcNotueNGR9tLAqU7RYbPL+g3W36cQsXCyO5euKgQQmd1lEumFxfRowI/lVmGrx0dJwSGO8LG33CTmVXJROImBUNEUKldnvWMbRc1we1RZGmY= Received: by 10.100.214.16 with SMTP id m16mr5599533ang.101.1206682834042; Thu, 27 Mar 2008 22:40:34 -0700 (PDT) Received: from noah.gleamynode.net ( [222.122.72.218]) by mx.google.com with ESMTPS id s30sm2839692elf.17.2008.03.27.22.40.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Mar 2008 22:40:32 -0700 (PDT) Received: from [116.34.136.157] (helo=[192.168.0.21]) by noah.gleamynode.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1Jf7KG-0003PH-4i; Fri, 28 Mar 2008 14:40:28 +0900 Subject: Re: how to use thread pool From: =?UTF-8?Q?=EC=9D=B4=ED=9D=AC=EC=8A=B9?= "(Trustin Lee)" To: users@mina.apache.org In-Reply-To: <8aebcd190803272223x29413d97r72680e58ce1d2fa3@mail.gmail.com> References: <8aebcd190803270159l7b8082b2j19c64e1f0bd530e3@mail.gmail.com> <8aebcd190803270226j26179b93ua95c10efc6a3ef80@mail.gmail.com> <1206671025.27115.8.camel@hermes> <8aebcd190803271939x6ca80180n61553c431430a733@mail.gmail.com> <1206679229.11302.1.camel@hermes> <8aebcd190803272223x29413d97r72680e58ce1d2fa3@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BVoWVrCXbgvZBfxjEDcy" Organization: http://gleamynode.net/ Date: Fri, 28 Mar 2008 14:40:26 +0900 Message-Id: <1206682826.11302.3.camel@hermes> Mime-Version: 1.0 X-Mailer: Evolution 2.22.0 X-Virus-Checked: Checked by ClamAV on apache.org --=-BVoWVrCXbgvZBfxjEDcy Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Please take a look at the JavaDoc of ServerSocket.bind() - you can specify backlog there. MINA also has the same property so you can adjust it. On Fri, 2008-03-28 at 14:23 +0900, ryan cheng wrote: > 2008/3/28, =EC=9D=B4=ED=9D=AC=EC=8A=B9 (Trustin Lee) : > > > > Probably you could increase the backlog of the acceptor? >=20 >=20 > I donot know the acceptor's backlog used for what? Can you explain that? > thanks. >=20 > You will also > > have to redesign your protocol so a client makes a connection only once > > and reuse it on and on, instead of opening and closing connections > > frequently. > > > > do you mean keep the IoSession is open, and reuse it? --=20 Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature is actually human habit -- http://gleamynode.net/ --=-BVoWVrCXbgvZBfxjEDcy Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBH7ITKHGKn3AJV7KYRAkKCAJ9vdltCH2zWWt2Esuhyg2EGhYBVhgCfV7wA dLCfCSfEaQrxksFahdxGfJM= =MOvk -----END PGP SIGNATURE----- --=-BVoWVrCXbgvZBfxjEDcy--