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 B2834987E for ; Tue, 20 Dec 2011 09:38:41 +0000 (UTC) Received: (qmail 5768 invoked by uid 500); 20 Dec 2011 09:38:41 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 5740 invoked by uid 500); 20 Dec 2011 09:38:41 -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 5722 invoked by uid 99); 20 Dec 2011 09:38:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 09:38:41 +0000 X-ASF-Spam-Status: No, hits=4.6 required=5.0 tests=HTML_MESSAGE,NO_RDNS_DOTCOM_HELO,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 98.139.253.105 is neither permitted nor denied by domain of harishs@yahoo-inc.com) Received: from [98.139.253.105] (HELO mrout2-b.corp.bf1.yahoo.com) (98.139.253.105) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 09:38:33 +0000 Received: from EGL-EX07CAS02.ds.corp.yahoo.com (egl-ex07cas02.eglbp.corp.yahoo.com [203.83.248.209]) by mrout2-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id pBK9brXV079619 for ; Tue, 20 Dec 2011 01:37:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1324373875; bh=chkUR5Ajo2SE/hckN7xFSLCwD9g5/6rk6hnW+ve0Kes=; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; b=TbcWB3dws2kk86VS/Fb2/lPvCJHBRsXh2+bhfjLBmRMhZ318n5U4Kznk50k0Fdw8Y MnoEqeQxI6sVlT07Pr3qqAgulSGmokzEX86fmn7Ge7K4xt9OL0WHjj3jJSpwmVRqJ3 PGATHZ5jpMnx9dlD9gQvld87uLWddmAOOLHn2iVI= Received: from EGL-EX07VS01.ds.corp.yahoo.com ([203.83.248.205]) by EGL-EX07CAS02.ds.corp.yahoo.com ([203.83.248.216]) with mapi; Tue, 20 Dec 2011 15:07:52 +0530 From: Harish Sharma To: "users@activemq.apache.org" Date: Tue, 20 Dec 2011 15:07:52 +0530 Subject: Backlog data causes producer to slow down. Thread-Topic: Backlog data causes producer to slow down. Thread-Index: Acy++wuMhnJo4hpJQLuYOvyv1iSdeg== Message-ID: <924C8723-0E88-43C0-82CD-2870DDC7E90B@yahoo-inc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_924C87230E8843C082CD2870DDC7E90Byahooinccom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_924C87230E8843C082CD2870DDC7E90Byahooinccom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I tried to reply to http://activemq.2283324.n4.nabble.com/Backlog-data-caus= es-producers-to-slow-down-tt3806018.html post . Because i am facing similar= issue. Whenever my consumer goes down and there is a data back log the production = rate goes down significantly. Moreover when my consumer is up again , the production rate goes down again= and this cycle repeats itself. Some Info : I am using ActiveMQ 5.5.1 , KahaDB message store, Producer flow control = =3D FALSE , AsyncSend(true) , persistence =3D true and ConcurrentQueueStore= AndDispatch =3D true and false (tried both does not make much difference) As i read in this post about cursors so i am using the default store cursor= . Here is snippet from broker.xml destinationPolicy> " optimizedDispatch=3D"true" memoryLimit= =3D"1gb" producerFlowControl=3D"false" /> " optimizedDispatch=3D"true" memoryLimit= =3D"1gb" producerFlowControl=3D"false" /> I am using all the optimizations(i read from http://fusesource.com/docs/bro= ker/5.4/tuning/index.html ) for producer , consumer and broker. These optimizations are able to increase message production rate a bit but = the main issue is the stability of the production rate.(why it goes down 10= times and then keep on going down with every time consumers goes down or g= oes up again). I am trying to figure out the cause but unable to pinpoint the code in acti= veMQ which is causing this issue. When i saw threads state in jconsole i found out that as soon as consumer s= tart running , producer thread goes into wait state ( State: WAITING on jav= a.util.concurrent.locks.AbstractQueuedSynchronizer ).I understand the queue= these producers write to is blocking queue.But i don't understand why con= sumers are affecting producers while flow control is off and my store size= is 500 GB and memory is 20GB .Why not producers are producing at a constan= t rate until my KahaDB store is full. I really need help in this matter and deeply appreciate any help from you g= uys. Thanks & Regards Harish Sharma --_000_924C87230E8843C082CD2870DDC7E90Byahooinccom_--