Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E7371884E for ; Fri, 17 Jul 2015 20:53:28 +0000 (UTC) Received: (qmail 67132 invoked by uid 500); 17 Jul 2015 20:53:24 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 67072 invoked by uid 500); 17 Jul 2015 20:53:24 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 67061 invoked by uid 99); 17 Jul 2015 20:53:24 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2015 20:53:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6CB801A726C for ; Fri, 17 Jul 2015 20:53:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.108 X-Spam-Level: X-Spam-Status: No, score=-1.108 tagged_above=-999 required=6.31 tests=[RCVD_IN_MSPIKE_H2=-1.108] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uVCciUsX5h3s for ; Fri, 17 Jul 2015 20:53:20 +0000 (UTC) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 3B6D442959 for ; Fri, 17 Jul 2015 20:53:20 +0000 (UTC) Received: by iebmu5 with SMTP id mu5so84728263ieb.1 for ; Fri, 17 Jul 2015 13:53:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=WlfbOZkSuhq33SowJyI8zA/RLpUx43Oz4ZfpImIVHlo=; b=gWJAX2D+meNhKU/DjU2zi1euyw2zh+yKbaV6SOGVnZ/qjfy3kgpUUoXo2BN3sKRtqr Bqql5EBaqKkG1pbZJQKvpQcSpk3Z9tWCj9UtHAsRThHa/swQrk6K+RC30hBi8sIcfES1 ASvJOwLJeU6r9FQK+Yx+CcNp7zYtu7dqEku3vMsZYu9mSKHWObJNBZ8oI0Oj+cLJDaPg jjwWqK3zH7bzVAUIPqbzM7ZDDT5ip8YHDMQ+k1CPkHVzkl3/eP5bRwNARn/ViiHyT3pM Ebi21Qz5X+OJH4VB7fGg7N65o5bvq+BdWRPr85idRAiOo+m+AUqvPbpKFb7il7fG4BgE +lGQ== X-Gm-Message-State: ALoCoQkfcAzJRuZ/opyVgp9J+cEF6IRw0qjk/vidzLn0PiyL7OMLna3jmP0Gs8XqQAiQA+f2vtxl MIME-Version: 1.0 X-Received: by 10.50.4.102 with SMTP id j6mr434753igj.40.1437166399858; Fri, 17 Jul 2015 13:53:19 -0700 (PDT) Received: by 10.36.61.142 with HTTP; Fri, 17 Jul 2015 13:53:19 -0700 (PDT) Date: Fri, 17 Jul 2015 16:53:19 -0400 Message-ID: Subject: Keeping http-8443 threads in check (Apache Tomcat/6.0.29) From: Brad Spry To: users@tomcat.apache.org Content-Type: text/plain; charset=UTF-8 After ingesting copious amounts of objects into Fedora Commons, the system returns to an idle state. However, even with the system idle, http-8443 residue remains behind, chewing up RAM and CPU for no good reason: "http-8443-16" daemon prio=10 tid=0x000000004237b800 nid=0x206a runnable [0x00007fb69deeb000] "http-8443-15" daemon prio=10 tid=0x0000000042215000 nid=0x2069 in Object.wait() [0x00007fb69dfed000] "http-8443-14" daemon prio=10 tid=0x0000000042145000 nid=0x2068 in Object.wait() [0x00007fb69dbae000] "http-8443-13" daemon prio=10 tid=0x0000000042008000 nid=0x2067 in Object.wait() [0x00007fb69ddd5000] "http-8443-12" daemon prio=10 tid=0x00000000420d0800 nid=0x1fc0 in Object.wait() [0x00007fb69bd3e000] "http-8443-11" daemon prio=10 tid=0x0000000041f6f000 nid=0x16ec in Object.wait() [0x00007fb69d9f8000] "http-8443-10" daemon prio=10 tid=0x0000000042907800 nid=0x8aa runnable [0x00007fb69b837000] "http-8443-9" daemon prio=10 tid=0x0000000043a50800 nid=0x7a1d in Object.wait() [0x00007fb69b738000] "http-8443-8" daemon prio=10 tid=0x0000000042248000 nid=0x7a1c in Object.wait() [0x00007fb69b61c000] "http-8443-7" daemon prio=10 tid=0x0000000041e94000 nid=0x764e runnable [0x00007fb69dcc6000] "http-8443-6" daemon prio=10 tid=0x000000004336a000 nid=0x6a1b runnable [0x00007fb69ba39000] "http-8443-5" daemon prio=10 tid=0x0000000042142800 nid=0x6a1a runnable [0x00007fb69be3e000] "http-8443-4" daemon prio=10 tid=0x000000004201d800 nid=0x6a19 runnable [0x00007fb69bb3a000] "http-8443-3" daemon prio=10 tid=0x0000000042238800 nid=0x6984 runnable [0x00007fb6a9fa1000] "http-8443-2" daemon prio=10 tid=0x0000000043133800 nid=0x6983 runnable [0x00007fb6aa5a7000] "http-8443-1" daemon prio=10 tid=0x000000004226f800 nid=0x5ee2 runnable [0x00007fb6aa9ab000] I've experimented with placing connectionTimeout="20000" on the AJP and org.apache.coyote.http11.Http11AprProtocol 's, but have observed no change in behavior. I'm writing to ask of anyone has any knowhow or advice for automatically pruning idle 's like this? Thank you ahead of time. Sincerely, Brad Spry Atkins Library UNC Charlotte --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org