From dev-return-20462-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Thu Aug 16 06:38:01 2007 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 32192 invoked from network); 16 Aug 2007 06:37:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Aug 2007 06:37:59 -0000 Received: (qmail 98735 invoked by uid 500); 16 Aug 2007 06:37:51 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 98709 invoked by uid 500); 16 Aug 2007 06:37:51 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 98696 invoked by uid 99); 16 Aug 2007 06:37:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2007 23:37:51 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 06:38:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D4DDC714191 for ; Wed, 15 Aug 2007 23:37:30 -0700 (PDT) Message-ID: <25038960.1187246250868.JavaMail.jira@brutus> Date: Wed, 15 Aug 2007 23:37:30 -0700 (PDT) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Updated: (DIRSERVER-1019) Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion In-Reply-To: <13402489.1187246250659.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Karasulu updated DIRSERVER-1019: ------------------------------------- Summary: Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion (was: Using same thread pool for I/O processing as request handling ) Improving title for clarity > Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion > -------------------------------------------------------------------------------------------------------------------- > > Key: DIRSERVER-1019 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1019 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.0.2, 1.0.1, 1.5.0, 1.0, 1.0-RC4, 1.0-RC3, 1.0-RC2, 1.0-RC1, pre-1.0 > Reporter: Alex Karasulu > Assignee: Alex Karasulu > Priority: Blocker > Fix For: 1.5.1, 1.0.3 > > > In the ServerContext factory the same thread pool is being used to process I/O > and request handling. This is depleting the thread pool rapidly causing the > server to hang under certain conditions. I caught this bug on a x86_64 machine > with multiple cores when the ReferralITest test was hanging. The right number > of connections and requests being processed could have caused this issue to > arrise. Regardless thankfully the issue appeared and Trustin found the cause > for it. > Trustin tracked the bug down to the way we misconfigured MINA's thread pools. > He is currently fixing the problem in trunk and I suspect the same issue exists > within the 1.0 branch. > I suspect this could have caused serious issues in performance if not causing > several load test clients to hang while others had requests processed. I > recommend reassessing performance metrics once again after this fix. There > should be a considerable boost. I think our impression that MINA was a > bottleneck may have been attributed to this misconfiguration issue. > Anyways once Trustin has the fix in trunk I will apply it to the 1.0 branch and > make sure all tests pass successfully. I am assigning this issue to myself > even though T is providing the fix so I can manage the application on the > 1.0 branch and document the results. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.