From users-return-31942-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Sat Sep 22 02:33:15 2012 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 2CE61D8B0 for ; Sat, 22 Sep 2012 02:33:15 +0000 (UTC) Received: (qmail 30881 invoked by uid 500); 22 Sep 2012 02:33:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 30839 invoked by uid 500); 22 Sep 2012 02:33:14 -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 30830 invoked by uid 99); 22 Sep 2012 02:33:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 02:33:14 +0000 X-ASF-Spam-Status: No, hits=1.6 required=5.0 tests=FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gaurav.cs.sharma@gmail.com designates 209.85.160.43 as permitted sender) Received: from [209.85.160.43] (HELO mail-pb0-f43.google.com) (209.85.160.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 02:33:06 +0000 Received: by pbbrq2 with SMTP id rq2so8343160pbb.2 for ; Fri, 21 Sep 2012 19:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=iO+h+AeqJm7hd0TFPz7K5NSmwrDHJwa16S+sRYd6qTA=; b=vL8r5354kfHOWLITYC9MqWtXtpGLCfzgYxr2iqaAo8dMRsNYaiSi+EAStM1Z/ZTuw1 cnayCeSvazzHOc+vlhrJao6PKjxsL2r0nhVqyGIaIhPsGLksbfeW6Xcpc8+oyRfkcKSb HY8nnrClJxKEWzjb6A/RmR1t9EbwogOx33InW1M9qUtF6Kqb06B8bQ/ixlNmzL26q/xE A6dCXRlpd5+fW1dBV6hLLouE2hGZOQCGu7b+NbIv5TaZFNaUh1V7GbWVvjGXMhcPsEDV jo2gH1xF7KQhSunPVmRjpJuuemkoPKr9P2DwQxq8TUZf1FHe+7oKNTRdAgOcCWQv0qjE PzYg== Received: by 10.66.88.197 with SMTP id bi5mr4978299pab.58.1348281165092; Fri, 21 Sep 2012 19:32:45 -0700 (PDT) Received: from [10.71.146.180] (mobile-198-228-220-075.mycingular.net. [198.228.220.75]) by mx.google.com with ESMTPS id l3sm4992949pay.2.2012.09.21.19.32.43 (version=SSLv3 cipher=OTHER); Fri, 21 Sep 2012 19:32:44 -0700 (PDT) Subject: Re: ActiveMQ Broker Scheduler unable to create new native thread References: <1348209293639-4656787.post@n4.nabble.com> From: Gaurav Sharma Content-Type: text/plain; charset=utf-8 X-Mailer: iPhone Mail (10A403) In-Reply-To: Message-Id: <3AF6A3D6-5EE3-47C3-A7B7-A662352DACC3@gmail.com> Date: Fri, 21 Sep 2012 19:32:39 -0700 To: "users@activemq.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) For starters, simply give it more heap. So, increase heap as a step function= (1G, 1.5G, 2G...) and measure throughput. Throughput sustenance will also d= epend on message size and how well both the broker and clients keep up. On Sep 21, 2012, at 18:49, jockeyyan wrote: > Dear Gaurav: >=20 > The configuration parameters of my broker as following: > --------------------------------------------------------------------------= ------------------------- > ACTIVEMQ_OPTS=3D-Xmx512M > -Dorg.apache.activemq.UseDedicatedTaskRunner=3Dfalse > -Djava.util.logging.config.file=3Dlogging.properties -Xss256k > --------------------------------------------------------------------------= ------------------------- > There are 1 CPU of 4 kernels and 6G memory on this machine, and no > other app is running. >=20 >=20 > 2012/9/21 Gaurav Sharma [via ActiveMQ] > : >> How much heap have we given to the broker and what else is running on the= >> same machine? Also, just fire up jconsole, attach to the process and watc= h >> allocations, threads and cpu - should give a clue. v5.6 is the current >> release, so, upgrade if possible. >>=20 >> On Sep 20, 2012, at 23:34, jockeyyan <[hidden email]> wrote: >>=20 >>> Hi: >>>=20 >>> I am using ActiveMQ 5.4.3 to make some loading test. I created one >>> producer, >>> one broker and one consumer with Spring JAX-WS config. The producer invo= ke >>> the functions to send messages to broker continuously and the consumer >>> just >>> receive and echo. >>> Everything is OK at beginning. After invoke many times(about 2000 to >>> 3000), >>> the broker is crashed and display the following error message, Does anyo= ne >>> could help me fingure out what the matter of the broker is? >>>=20 >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>> Exception in thread "ActiveMQ Broker[localhost] Scheduler" >>> java.lang.OutOfMemory >>> Error: unable to create new native thread >>> at java.lang.Thread.start0(Native Method) >>> at java.lang.Thread.start(Thread.java:640) >>> at >>> java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(Thr >>> eadPoolExecutor.java:727) >>> at >>> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.ja >>> va:657) >>> at >>> org.apache.activemq.thread.PooledTaskRunner.wakeup(PooledTaskRunner.j >>> ava:76) >>> at >>> org.apache.activemq.broker.region.Queue.asyncWakeup(Queue.java:1637) >>> at >>> org.apache.activemq.broker.region.Queue.expireMessages(Queue.java:773 >>> ) >>> at >>> org.apache.activemq.broker.region.Queue.access$100(Queue.java:83) >>> at org.apache.activemq.broker.region.Queue$2.run(Queue.java:123) >>> at >>> org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask. >>> java:33) >>> at java.util.TimerThread.mainLoop(Timer.java:512) >>> at java.util.TimerThread.run(Timer.java:462) >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>>=20 >>> The config of my consumer as following: >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>> >> class=3D"org.springframework.jms.connection.CachingConnectionFactory"> >>> >>> >>> >>> >>> >>> >>> >>>=20 >>> >> p:connectionFactory-ref=3D"jmsConnectionFactory" >>> p:targetDestination=3D"test.queue" >>> /> >>>=20 >>>=20 >>> >> id=3D"CustomerServiceHTTP" address=3D"jms://" >>>=20 >>> implementor=3D"com.example.customerservice.server.CustomerServiceImpl"> >>> >>> >>> >> p:jmsConfig-ref=3D"jmsConfig" /> >>> >>> >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>>=20 >>> The config of my producer as following: >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>> >> class=3D"org.springframework.jms.connection.SingleConnectionFactory"> >>> >>> >>> >>> >>> >>> >>>=20 >>> >> p:connectionFactory-ref=3D"jmsConnectionFactory" >>> p:targetDestination=3D"test.queue" >>> /> >>>=20 >>> >> address=3D"jms://" >>> serviceClass=3D"com.example.customerservice.CustomerService"> >>> >>> >>> >> p:jmsConfig-ref=3D"jmsConfig" /> >>> >>> >>>=20 >>> ------------------------------------------------------------------------= -------------------------- >>>=20 >>> Jockey Yan >>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> View this message in context: >>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unable-t= o-create-new-native-thread-tp4656787.html >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>=20 >>=20 >> ________________________________ >> If you reply to this email, your message will be added to the discussion >> below: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-Broker-Scheduler-unable-to= -create-new-native-thread-tp4656787p4656820.html >> To unsubscribe from ActiveMQ Broker Scheduler unable to create new native= >> thread, click here. >> NAML >=20 >=20 >=20 > --=20 > =E9=97=AB=E7=BB=A7=E5=9F=B9 > Jockey Yan >=20 > Email: jockeyyan@gmail.com > Mobile: 13601186611 >=20 >=20 >=20 >=20 > -- > View this message in context: http://activemq.2283324.n4.nabble.com/Active= MQ-Broker-Scheduler-unable-to-create-new-native-thread-tp4656787p4656827.htm= l > Sent from the ActiveMQ - User mailing list archive at Nabble.com.