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 3575BE336 for ; Wed, 27 Feb 2013 19:31:51 +0000 (UTC) Received: (qmail 83658 invoked by uid 500); 27 Feb 2013 19:31:50 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 83629 invoked by uid 500); 27 Feb 2013 19:31:50 -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 83619 invoked by uid 99); 27 Feb 2013 19:31:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 19:31:50 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of raul@evosent.com designates 209.85.210.181 as permitted sender) Received: from [209.85.210.181] (HELO mail-ia0-f181.google.com) (209.85.210.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 19:31:43 +0000 Received: by mail-ia0-f181.google.com with SMTP id w33so778530iag.40 for ; Wed, 27 Feb 2013 11:31:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:in-reply-to:mime-version:date:message-id :subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=VHOiZ1eeX4VLKog9a2IT3PKjruBJDZqqsHA7P3xLez4=; b=W7zF70M4O/kehH+6pVTHKB37GEtlepp+FUI8QAoh0IEjLkCvyE9cX8HTFqVJ58VwE9 7d8JL05e51GaSZPGa4Y+eWaj5j4XyM3HF6YOJtZAwNOZOd8jlz73KKES30/Rtreh7ZA+ Z1rqJfARtWyHycbAHz4hDTLVfpF62SPf6hmOiR6IUeWbs4vhg9qqypa719SDJHVPMYLI DSZAHQ9dBZlUWIiCasWvgeSwBjkI1nVp0bWnJo6cuQZiZLe1s9r87PFUiSeOg10+Swj5 OHIVWRc1cFDFG1vjmJ6bPSGdLuKTjBqjKSl7UHEmFpssqeJ5ONYQu/RR2UT5s3Xe50/I w6zw== X-Received: by 10.50.182.137 with SMTP id ee9mr1704931igc.96.1361993482525; Wed, 27 Feb 2013 11:31:22 -0800 (PST) References: <1360925085840-4663532.post@n4.nabble.com> <1361979614423-4664204.post@n4.nabble.com> From: Raul Kripalani In-Reply-To: <1361979614423-4664204.post@n4.nabble.com> Mime-Version: 1.0 (1.0) Date: Wed, 27 Feb 2013 19:31:22 +0000 Message-ID: <-1477429753479544072@unknownmsgid> Subject: Re: AMQ halts and crashes after few thousand reqs To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmF2Ju/VoUbECUrKhlx4p7vg069I1WaklH5TxCMxRnFP204dMSg4oq3G7Zlzq6RNsQdYWDw X-Virus-Checked: Checked by ClamAV on apache.org A likely explanation for such a graph is that you're using VM cursors and your consumers are slow. Therefore your messages are piling up in memory. I wonder if producer flow control is enabled at all and why the constant pending message limit strategy is not ditching old messages. Unless you post your broker XML configuration soon, no one will be able to help you any further. Regards, Ra=FAl. Sent from my iPad On 27 Feb 2013, at 15:40, "mandar.wanpal" wrote: > Hi All, > > Thanks for the replies. From the replies above, I could understand 2 thin= gs. > 1. I need to post detailed config. (Christian) > 2. There are cases of AMQ running fine with people. (Gaurav) > > Firstly, configs. > Below are startup jvm params. > /usr/lib/jvm/java-1.6.0-sun.x86_64/bin/java -Xms1g -Xmx1g -Xss256k > -Dorg.apache.activemq.UseDedicatedTaskRunner=3Dfalse > -Djava.util.logging.config.file=3Dlogging.properties > -verbose:gc > -XX:PermSize=3D128m > -XX:MaxPermSize=3D128m > -Xloggc:/opt/app/apache-activemq/data/amq_gcstats.log > -Dcom.sun.management.jmxremote.port=3D1099 > -Dcom.sun.management.jmxremote.authenticate=3Dfalse > -Dcom.sun.management.jmxremote.ssl=3Dfalse > -Dcom.sun.management.jmxremote > -Dactivemq.classpath=3D/opt/app/apache-activemq/conf; > -Dactivemq.home=3D/opt/app/apache-activemq > -Dactivemq.base=3D/opt/app/apache-activemq > -Dactivemq.conf=3D/opt/app/apache-activemq/conf > -Dactivemq.data=3D/opt/app/apache-activemq/data > -Djava.io.tmpdir=3D/opt/app/apache-activemq/tmp > -jar /opt/app/apache-activemq/bin/run.jar start > > > @Gaurav: > Yes this system is not a productive system where I am doing load testing = and > its not even quadcore. Its dualcore. But, my productive system is also no= t > that high end because we are at very initial stage in this project and we > may ramp up these systems as per the requirements. I have production syst= em > with dual core 2.67Ghz processor with 8G RAM > From the config I have provided above, If you could help me find out > potential areas where this config can be improved for such setup. > Will it be too much to expect 10 messages/sec with such setup. > > Also main concern I had mentioned was with the increasing FullGC which > ultimately results in AMQ not responding and it switches to its failover > (which also fails at some point). Have you observed any such thing at you= r > end. I have seen jvm stats via jconsole while these tests. below are the > jconsole stats. > heapusage_amq.jpg > > VMSummary.jpg > > > I will attach activemq.xml ASAP. > > > > > ----- > Regards, > Mandar Wanpal > Email: mandar.wanpal@gmail.com > -- > View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-h= alts-and-crashes-after-few-thousand-reqs-tp4663532p4664204.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.