Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 70881 invoked from network); 12 Jan 2010 12:19:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2010 12:19:31 -0000 Received: (qmail 24228 invoked by uid 500); 12 Jan 2010 12:19:31 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 24168 invoked by uid 500); 12 Jan 2010 12:19:30 -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 24158 invoked by uid 99); 12 Jan 2010 12:19:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2010 12:19:30 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.218.215 as permitted sender) Received: from [209.85.218.215] (HELO mail-bw0-f215.google.com) (209.85.218.215) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2010 12:19:21 +0000 Received: by bwz7 with SMTP id 7so16041280bwz.6 for ; Tue, 12 Jan 2010 04:19:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=P91ep7Hgp5iBi8Lpu3mm9fgCxlyQswKwCABK6NSEdhQ=; b=s6rYPpery9GNT6eqM81/VpFDUSMxNYhplwAz6OMmpo/KdUrpvsQe1wrdiwlEK+pygK jebJ7I1BwRx3pHtBj3vF904AISw5Cd/+QJGwZd8goTW5WqNHV5/6LHmz4WFpy2RGFixp y+Y2PddBnbz0ZpN2SYp7PDNaJbqxqB54Nho8w= 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; b=paYUrcHShlj/NeyEdesi2I+HVChfD1HpnEJ/DBEM63A2Kgcro+YFE0LGd1b+PrhkBC h1pILMYTx1+P0Dlz7BfVtqs4LwBdVQBltNX3rO94KOoecph/MQMOexaWy18KXSjxYHfT elT8jzZHfuYl0o2yYwbYXPO2hF2AXOWTqs3No= MIME-Version: 1.0 Received: by 10.204.155.86 with SMTP id r22mr158494bkw.165.1263298740339; Tue, 12 Jan 2010 04:19:00 -0800 (PST) In-Reply-To: <27126558.post@talk.nabble.com> References: <27126558.post@talk.nabble.com> Date: Tue, 12 Jan 2010 12:19:00 +0000 Message-ID: <3a73c17c1001120419q5a68771cx5b13b1840dac1a4a@mail.gmail.com> Subject: Re: Thread for each client From: Gary Tully To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=0015175ce154a9c460047cf6a802 --0015175ce154a9c460047cf6a802 Content-Type: text/plain; charset=ISO-8859-1 With a normal disconnect from a java client those reader threads should disappear. With an abnormal disconnect, where the socket is not fully closed, it can take some time (os tcp config dependent) for the broker to identify the connection as closed. What does netstat tell you about the active connections to the brokers listen port. Are there a bunch of sockets in timed wait state? 2010/1/12 marcin80 > > Hi, > > I'm using ActiveMQ 5.2 and I've noticed thad ActiveMQ create new thread for > every connection but even the client will disconnect its thread still alive > (state RUNNABLE). It is ActiveMQ normal behavior? > Can I change this? I would like to finalize thread if client will > dissconnect. > > Cheers, > Marcin > -- > View this message in context: > http://old.nabble.com/Thread-for-each-client-tp27126558p27126558.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com --0015175ce154a9c460047cf6a802--