Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 79781 invoked from network); 19 Mar 2008 08:11:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2008 08:11:24 -0000 Received: (qmail 43561 invoked by uid 500); 19 Mar 2008 08:11:22 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 43535 invoked by uid 500); 19 Mar 2008 08:11:22 -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 43526 invoked by uid 99); 19 Mar 2008 08:11:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 01:11:22 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 08:10:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A5FF6234C0A7 for ; Wed, 19 Mar 2008 01:09:32 -0700 (PDT) Message-ID: <1184919854.1205914172678.JavaMail.jira@brutus> Date: Wed, 19 Mar 2008 01:09:32 -0700 (PDT) From: "Moti Tal (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQ-1626) Active MQ version 5.X - java 5 - memory leaks In-Reply-To: <1771753397.1205905892731.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/activemq/browse/AMQ-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41712#action_41712 ] Moti Tal commented on AMQ-1626: ------------------------------- What does it mean? ActiveMQ 5.x can't work with JDK 5 at all, as for memory leaks? > Active MQ version 5.X - java 5 - memory leaks > ---------------------------------------------- > > Key: AMQ-1626 > URL: https://issues.apache.org/activemq/browse/AMQ-1626 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.0.0, 5.1.0 > Reporter: Michal Singer > Priority: Blocker > Attachments: ClientExecuterController.java, JmsListener.java, JmsResponseSender.java > > > when working with jdk1.5 and activemq 5.X. there are problems with memory leaks. > I use an embedded broker configured in spring 2.0.8. > I have a client application (producer ) and a server (consumer) which inside it the broker. > The client uses PooledConnectionFactory, creates one connection, 2 sessions (receive and send), and 1 producer. > the client connects to 2 queues defined in the broker (configured in spring), and sets the "reply to" to a temporary queue. > The server receives the messages from the client, does some processing, and returns a reply on the temp q. > each request is handled by a diiferent temp q. the temp q is deleted once the client receives the responses. > All resources are deleted on client side. the server is hanlded by spring. the server responses on the temp queues. > During run, i see a few problems (in jconsole) > 1. memory of broker increases gradually and never released > 2. memory of temp queues increases gradually and never released > 3. advisory topic node is created with many objects under it - which seem like with the same ids as some of the temp queue. they accumulate, > and are never released. > These leaks prevent me from working,. the activemq will stop working after a few hours due to 100%memory consumption. > There are also memory leaks concerning temp queues usage. > I tried creating one connection on client or using a pool of connections but nothing helped. > It looks like some memory leak on the temp queues. > Do you have a work around for these problems, when will there be fixes for these problems? > If i will use a static queues, will all the leaks in the broker be solved? > If i create a new connection for each request process, should this solve the problem? (checked - does not work) > I attached the client (producer) code and the server (consumer) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.