From dev-return-28456-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Thu Sep 8 14:43:33 2011 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 568DC70B9 for ; Thu, 8 Sep 2011 14:43:33 +0000 (UTC) Received: (qmail 49428 invoked by uid 500); 8 Sep 2011 14:43:33 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 48469 invoked by uid 500); 8 Sep 2011 14:43:31 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 48134 invoked by uid 99); 8 Sep 2011 14:43:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Sep 2011 14:43:31 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Sep 2011 14:43:29 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 8B75A88D23 for ; Thu, 8 Sep 2011 14:43:09 +0000 (UTC) Date: Thu, 8 Sep 2011 14:43:09 +0000 (UTC) From: "Carl Allain (JIRA)" To: dev@activemq.apache.org Message-ID: <316316417.3194.1315492989568.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1701001251.34173.1313177427899.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (AMQ-3448) Zombie ActiveMQ Connection Dispatcher threads - seems to consume all process File Descriptors (FD leak) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100358#comment-13100358 ] Carl Allain commented on AMQ-3448: ---------------------------------- Seems too like the host from where the leaking threads/connections come from is creating a connection everysecond or so. Could it be the problem? From the dev team, I obtained the "spring" config: > Zombie ActiveMQ Connection Dispatcher threads - seems to consume all process File Descriptors (FD leak) > ------------------------------------------------------------------------------------------------------- > > Key: AMQ-3448 > URL: https://issues.apache.org/jira/browse/AMQ-3448 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.3.2 > Environment: Active MQ 5.3.2 > java version "1.6.0_23" > Java(TM) SE Runtime Environment (build 1.6.0_23-b05) > Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode) > LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch > Distributor ID: CentOS > Description: CentOS release 5.5 (Final) > Release: 5.5 > Codename: Final > Reporter: Carl Allain > Priority: Critical > > Somehow linked to https://issues.apache.org/jira/browse/AMQ-3286 which was closed. I am opening here as I cannot reopen the old bug and I hope that with the information I provide here, someone will be able to have some insight of the possible cause and a fix. > I don't know how to reproduce with a test case, but I have found 800+ of such "ActiveMQ Connection Dispatcher" threads. I also noted that the number of FDs for the process keeps increasing and after a few days, we have a "too many files opened" when going beyond the 1024 limit. Most of those FDs (hundreds) do look like: > java 6700 lexo-ext 904u sock 0,5 1741176200 can't identify protocol > There is not much activity on the system and that is still enough to get the problem. > When we reach the limit of FDs, we get tons of stack traces in the logs, filling up the hard disk... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira