Return-Path: 
 <dev-return-27049-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
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 3E0CB600D
	for <apmail-activemq-dev-archive@www.apache.org>;
 Tue,  7 Jun 2011 11:22:21 +0000 (UTC)
Received: (qmail 43431 invoked by uid 500); 7 Jun 2011 11:22:21 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 43398 invoked by uid 500); 7 Jun 2011 11:22:21 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 43389 invoked by uid 99); 7 Jun 2011 11:22:21 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 11:22:21 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_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; Tue, 07 Jun 2011 11:22:19 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id D77BA970FF
	for <dev@activemq.apache.org>; Tue,  7 Jun 2011 11:21:58 +0000 (UTC)
Date: Tue, 7 Jun 2011 11:21:58 +0000 (UTC)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <902444170.111.1307445718879.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1076310997.571.1307370898987.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (AMQ-3358) ActiveMQ JMXConnectorFactory is not
 calling close causing thousands of threads to be created
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-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac reassigned AMQ-3358:
----------------------------------

    Assignee: Dejan Bosanac

> ActiveMQ JMXConnectorFactory is not calling close causing thousands of threads to be created
> --------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3358
>                 URL: https://issues.apache.org/jira/browse/AMQ-3358
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.5.0
>         Environment: Occurs on RHEL 5 and Mac OS
>            Reporter: Reid Morrison
>            Assignee: Dejan Bosanac
>
> We have run into a problem in production where our ActiveMQ 5.5 Broker eventually uses thousands of threads. Doing a thread stack dump we have thousands of the following entries:
> "JMX server connection timeout 127937" daemon prio=10 tid=0x000000001c215000 nid=0x1734 in Object.wait() [0x00002aabd7c97000]
>    java.lang.Thread.State: TIMED_WAITING (on object monitor)
>         at java.lang.Object.wait(Native Method)
>         at com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:150)
>         - locked <0x00002b74ffe91938> (a [I)
>         at java.lang.Thread.run(Thread.java:619)
> We are using Hyperic HQ to monitor ActiveMQ remotely over JMX.
> To reproduce the problem in a stand-alone environment (without needing Hyperic) :
> 1. Start ActiveMQ 5.5 Broker
> 2. Connect to ActiveMQ using JConsole and then disconnect
> 3. Force a thread dump on the ActiveMQ broker process as follows:
>    kill -QUIT <activemq-pid>
> 4. After every JConsole connection to the Broker process the following additional thread is created:
> "JMX server connection timeout 128" daemon prio=5 tid=1030bd000 nid=0x1108f8000 in Object.wait() [1108f7000]
> Under ActiveMQ 5.4.2-Fuse-03-09 we do not see this issue. Is there an existing patch somewhere that has just not been applied to 5.5?
> Someone else with the same issue:
> http://web.archiveorange.com/archive/v/hXOgqMGA78WNhT5lpmKX
> We found more info on closing the JMX connection:
> http://forums.oracle.com/forums/thread.jspa?threadID=1665966&tstart=0
> We are willing to make and submit a patch with a little guidance on where we should call the close() on JMXConnectorFactory.
> It appears the source file where the change should be made is:
> activemq-core/src/main/java/org/apache/activemq/broker/jmx/ManagementContext.java
> Any help is appreciated.
> Thank you,
> Reid

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira