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 1B4121418 for ; Tue, 19 Apr 2011 13:06:08 +0000 (UTC) Received: (qmail 65094 invoked by uid 500); 19 Apr 2011 10:19:28 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 65063 invoked by uid 500); 19 Apr 2011 10:19:28 -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 65050 invoked by uid 99); 19 Apr 2011 10:19:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 10:19:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qw0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 10:19:23 +0000 Received: by qwf6 with SMTP id 6so3973641qwf.2 for ; Tue, 19 Apr 2011 03:19:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=r22H1vu3CSxhFNzXx1P9bF/Jtzjt4fzB9Knh7VMhq8o=; b=qLkwjM2Vg+yVpIKePQH8UHMz+Zn3oTW+yE0EyfbvKVXrV50hm/yEHll+XmbDPT+DHE kk6EN6NB91j5S/AvGUlsVu6kf/lyB+Lw/kE63f/TJiXPX9b/VOEm3bLujF0wqB9RVHMH +iYHF7GDwMxiinZ32amvk/2uC22BUX3MqRV8I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=qYlC5WmzT4ydyvcYq8RzVjpN2qS4SOLy7Vhr3HM2kM6WFpsHU3FPUi+OIDiBz355n3 oZIdIzfmoSSeIop4sogMnLW9gxP9NYMQNLW2fPnoqXoaY5ocrQvx+JqsiNN2REGg8aL6 896/zuTy8OvtQRO8BPbHipda+PrxJDrj33Oec= MIME-Version: 1.0 Received: by 10.224.211.66 with SMTP id gn2mr4376656qab.72.1303208342822; Tue, 19 Apr 2011 03:19:02 -0700 (PDT) Received: by 10.229.73.197 with HTTP; Tue, 19 Apr 2011 03:19:02 -0700 (PDT) In-Reply-To: <4DAC56E1.2070404@iweb.com> References: <4DAC56E1.2070404@iweb.com> Date: Tue, 19 Apr 2011 11:19:02 +0100 Message-ID: Subject: Re: ActiveMQ Connection Dispatcher thread From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can you open a jira issue to track this and attach your logs and specify the version. That looks like a bug. On 18 April 2011 16:21, Simon-Pierre LeBel wrote: > Hi, > > I'm having some issues with ActiveMQ Connection Dispatcher threads. > Whenever I get an InactivityIOException the thread goes into the Waiting > state and a new thread is started. > > =3D=3D activemq.log =3D=3D > 2011-04-18 10:15:31,244 | ERROR | Could not accept connection : > org.apache.activemq.transport.InactivityIOException: Channel was > inactive for too long: /127.0.0.1:35401 | > org.apache.activemq.broker.TransportConnector | ActiveMQ Task > > =3D=3D jstack =3D=3D > "ActiveMQ Connection Dispatcher: /127.0.0.1:35401" daemon prio=3D10 > tid=3D0x00007f10e440f800 nid=3D0x63e9 in Object.wait() [0x00007f10ce57800= 0] > =A0 java.lang.Thread.State: WAITING (on object monitor) > =A0 =A0 =A0 =A0at java.lang.Object.wait(Native Method) > =A0 =A0 =A0 =A0at java.lang.Object.wait(Object.java:485) > =A0 =A0 =A0 =A0at > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunne= r.java:105) > =A0 =A0 =A0 =A0- locked <0x00007f113bbd4618> (a java.lang.Object) > =A0 =A0 =A0 =A0at > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.= java:36) > > After running ActiveMQ for a couple of weeks there are more than 3k > waiting threads doing nothing but wasting memory. =A0If i disable the > inactivity monitor the problem goes away > (wireFormat.maxInactivityDuration=3D0). Is this a known bug ? > > My configuration: > - ActiveMQ 5.3.0 > - Pure Master/Slave > - Openwire enabled > - Flow Control enabled > - KahaDB > > Let me know if you need more informations. I can provide config file and > logs if needed. > > -- > Simon-Pierre LeBel [iWeb] > IT Architecture Specialist / Technical Lead > Sp=E9cialiste de l'Architecture TI / Leader Technique > http://www.iWeb.com/ > > --=20 http://blog.garytully.com http://fusesource.com