Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-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 B902CFBCF for ; Tue, 16 Apr 2013 23:24:59 +0000 (UTC) Received: (qmail 53717 invoked by uid 500); 16 Apr 2013 23:24:59 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 53686 invoked by uid 500); 16 Apr 2013 23:24:59 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 53678 invoked by uid 99); 16 Apr 2013 23:24:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 23:24:59 +0000 X-ASF-Spam-Status: No, hits=3.1 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smithh032772@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 23:24:53 +0000 Received: by mail-we0-f172.google.com with SMTP id r3so806590wey.3 for ; Tue, 16 Apr 2013 16:24:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=SXliqjslaoBPh9Gxp9Y1tJAeXhJjCFmvXVEUHFboXDY=; b=pT1ZOT/DEINpcjbzQGRZB2U4GDwSITYzAV48sxRksqYFnbRqj/BhK03OsgejZllYkz Tg5M/Yf4e8wU2LdWj4EfXtz06FXRgq5et/ouKRHx8SRUKg9ZnWC5X68pmjDBKKhut0T7 VWWxhyU/i3o9UWAH6ynHiX7NeoDYP4avviEyaCESMfZCBcv+xTtDEnMedk1p2U4vOunG wmXyqODZUNwn76SUPC+wyJoJLlYmL/6F5e42aL3L9gen66hIpDTxNOMTFWBcEBVEhtwv Q2YNnFKXAmkRJhZ8Rl4X7ey4s5QNowhGPtbjNwOmgNIgUEY16VcZ9kJXPv0X4q//lQM0 v/pw== MIME-Version: 1.0 X-Received: by 10.194.176.195 with SMTP id ck3mr7377052wjc.5.1366154673079; Tue, 16 Apr 2013 16:24:33 -0700 (PDT) Received: by 10.227.59.74 with HTTP; Tue, 16 Apr 2013 16:24:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 16 Apr 2013 19:24:32 -0400 Message-ID: Subject: Re: [Memory leak ] The web application appears to have started a thread. From: "Howard W. Smith, Jr." To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=089e013d0a3eff508504da82ab5f X-Virus-Checked: Checked by ClamAV on apache.org --089e013d0a3eff508504da82ab5f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable About a month ago, I started using ActiveMQ (v5.8.0) that is bundled with TomEE (v1.6.0), and i noticed that in the log too, when I stopped TomEE (to deploy new version of WAR file). so, I searched google, and found the following, http://activemq.2283324.n4.nabble.com/Old-issue-Memory-leak-after-stop-web-= application-in-Tomcat-td4653959.html which referenced the following, https://issues.apache.org/jira/browse/AMQ-3451 I found them both to be informative, and I think a fix was introduced in ActiveMQ 5.7.0, and the end result is that, even though your tomcat/tomee log mentions those possible memory leaks... if you examine your threads 'after' tomcat/tomee is stopped, then you will not see those threads any longer. At least, that is the case for me, since I'm using ActiveMQ 5.8.0 via TomEE+ 1.6.0. :) On Tue, Apr 16, 2013 at 5:22 PM, Leonardo Torres wrote: > Hi guys, > > I=B4m using AMQ 5.7.0 with Spring 3.0.1 and tomcat 7.0.19 as servlet > container. So, when my application starts, it=B4s ok, but when the tomcat > stop, I see in the console the follow lines: > > > "SEVERE: The web application [] appears to have started a thread named > [ActiveMQ InactivityMonitor Worker] but has failed to stop it. This is ve= ry > likely to create a memory leak. > Apr 16, 2013 2:43:21 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [] is still processing a request that has yet > to finish. This is very likely to create a memory leak. You can control " > > How can I stop these threads ? > > My jms-context.xml (Spring context) : > > class=3D"org.apache.activemq.ActiveMQConnectionFactory"> > > > > class=3D"org.apache.activemq.pool.PooledConnectionFactory"> > > > > Thank=B4s in advance > -- > Obrigado > Leonardo Torres. > --089e013d0a3eff508504da82ab5f--