Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 85985 invoked from network); 20 Jan 2010 09:11:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2010 09:11:13 -0000 Received: (qmail 32427 invoked by uid 500); 20 Jan 2010 09:11:13 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 32362 invoked by uid 500); 20 Jan 2010 09:11:13 -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 32352 invoked by uid 99); 20 Jan 2010 09:11:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 09:11:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 09:11:02 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NXWaH-00035S-4O for users@activemq.apache.org; Wed, 20 Jan 2010 01:10:41 -0800 Message-ID: <27238638.post@talk.nabble.com> Date: Wed, 20 Jan 2010 01:10:41 -0800 (PST) From: moreno9000 To: users@activemq.apache.org Subject: Re: Thread for each client In-Reply-To: <1A806507-2C9D-4029-B07F-2D5A3D1EB23F@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: moreno.mauri@italtel.it References: <27126558.post@talk.nabble.com> <27223897.post@talk.nabble.com> <44114721-397D-4778-944E-989AF4AB573C@gmail.com> <27228469.post@talk.nabble.com> <1A806507-2C9D-4029-B07F-2D5A3D1EB23F@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org To disable JMX must I set useJms="false" in section of activemq.xml? If I disable JMX, will it be possible to use AMQ Console to monitor the broker? In client code I call some MBean methods (for example queue.purge()). No JMX means no possibility to call mbean methods or two things aren't connected? Thanks Moreno rajdavies wrote: > > that'll be the jmx implementation - which is part of the JRE - can you > run with out jmx ? > > On 19 Jan 2010, at 16:25, moreno9000 wrote: > >> >> Hi rajdavies, >> I see a lot of threads like this one: >> >> "JMX server connection timeout 6925" daemon prio=10 tid=0x08faf000 >> nid=0x2759 in Object.wait() [0xac0ae000..0xac0af130] >> java.lang.Thread.State: TIMED_WAITING (on object monitor) >> at java.lang.Object.wait(Native Method) >> - waiting on <0xd5fcec60> (a [I) >> at com.sun.jmx.remote.internal.ServerCommunicatorAdmin >> $Timeout.run(Unknown >> Source) >> - locked <0xd5fcec60> (a [I) >> at java.lang.Thread.run(Unknown Source) >> >> Thanks >> Moreno >> >> >> rajdavies wrote: >>> >>> Hi moreno, >>> >>> can you take a stack trace of the broker ? - the threads should be >>> getting garbage collected >>> >>> thanks, >>> >>> Rob >>> On 19 Jan 2010, at 10:37, moreno9000 wrote: >>> >>>> >>>> I confirm Marcin's problem (with AMQ 5.3). >>>> >>>> One producer (java application with transport=openwire) >>>> For each message producer open a Connection, send a msg, close the >>>> Connection. >>>> >>>> Server side no problem for what concern file descriptors opened, >>>> memory usage, socket opened (with netstat I see all >>>> conn=ESTABLISHED). >>>> >>>> Problems with threads. >>>> >>>> A new thread is created (inside AMQ) for every producer's open-send- >>>> close. >>>> Threads don't disappear even if producer call connection.close() >>>> (they disappear after 20-30 seconds from producer's death). >>>> >>>> In activemq.xml I set producerFlowControl=false, >>>> transport.closeAsync=false. >>>> >>>> AMQ run with these options: >>>> -Xmx1024M, -Dorg.apache.activemq.UseDedicatedTaskRunner=false. >>>> >>>> Producer set jms.useAsyncSend=false. >>>> >>>> Are there other configurations I can try to stop thread's increment? >>>> >>>> Many thanks >>>> Moreno >>>> >>>> >>>> >>>> >>>> marcin80 wrote: >>>>> >>>>> 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- >>>> tp27126558p27223897.html >>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>> >>> >>> Rob Davies >>> http://twitter.com/rajdavies >>> I work here: http://fusesource.com >>> My Blog: http://rajdavies.blogspot.com/ >>> I'm writing this: http://www.manning.com/snyder/ >>> >>> >>> >>> >>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Thread-for-each-client-tp27126558p27228469.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > Rob Davies > http://twitter.com/rajdavies > I work here: http://fusesource.com > My Blog: http://rajdavies.blogspot.com/ > I'm writing this: http://www.manning.com/snyder/ > > > > > > > -- View this message in context: http://old.nabble.com/Thread-for-each-client-tp27126558p27238638.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.