Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 65958 invoked from network); 14 May 2009 12:00:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 May 2009 12:00:47 -0000 Received: (qmail 55731 invoked by uid 500); 14 May 2009 12:00:47 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55642 invoked by uid 500); 14 May 2009 12:00:47 -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 55621 invoked by uid 99); 14 May 2009 12:00:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 12:00:45 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.220.168 as permitted sender) Received: from [209.85.220.168] (HELO mail-fx0-f168.google.com) (209.85.220.168) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 12:00:35 +0000 Received: by fxm12 with SMTP id 12so1606397fxm.38 for ; Thu, 14 May 2009 05:00:13 -0700 (PDT) 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 :content-transfer-encoding; bh=ZQmaAj7g4CfDXJV029UPPtqy3SEMNEijdXmQrQjfHUE=; b=u6Hn5aXrJG/ETdSc+gkURCTW7znjJ+rutNZ8DxjSfxbsmAA8pO3f2G8WQQGhdUVEU2 iMat1U2aALA/4PUy2/6xE4ayCxb2c6JhCjsM5X7GY04Yo9vF0v+ppy0DiQmq+rcGFmzu pdWQ336LSG0M1AH4erOfxoF7tuXtzB5Oy+IIw= 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:content-transfer-encoding; b=dE7Zhy2wzygXAcWAjAX2eVYoyVbnxjGzTSv/ZR/rKPBW7E+7uh5JhreXXuSH6wA7OU c3k4ZvOId2Z1rxvu1NZBpsM13m0f1hZ8FORljvcAL0KeG5lkA+yRxp0SsQLs2IVm0U9C vBfje2YUjlDCiuzL77DE7zfyGS21Oz5Oxni40= MIME-Version: 1.0 Received: by 10.86.59.2 with SMTP id h2mr2411803fga.73.1242302413804; Thu, 14 May 2009 05:00:13 -0700 (PDT) In-Reply-To: <23538009.post@talk.nabble.com> References: <23538009.post@talk.nabble.com> Date: Thu, 14 May 2009 13:00:13 +0100 Message-ID: <3a73c17c0905140500u3eaee343nf55e492ec9cbf93b@mail.gmail.com> Subject: Re: Publishing to Topic is very slow in higher loads ActiveMQ5.2. From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org can you give more memory resources to the broker? I imagine there is some spooling to disk under high load. It may make sense to post your activemq.xml. 2009/5/14 KumarR : > > Hi All , > > I am having problem with publishing messages to Topic. It's taking too mu= ch > time to publish a message. Below are the details. > > Test Case: > > The Client =A0is publishing messages to RequestQueue. and waiting respons= es on > ResponseTopic using a co-relation id. > Server program consuming messages from RequestQueue using Spring Message > POJOs. These POJOs after consuming and processing the messages, > forms the response message and publishes to the ResponseTopic using > co-relationid. > The client using blocked receive(TIMEOUT) receive responses from > ResponseTopic using Message selector with co-relation id. > > > Observations: at higher loads, around 3000 conc users, the publishing > response messages back to Response Topic becoming slow; > taking around 5 secs to 10 secs. otherwise in 2000 conc users load, it wa= s > taking around 100 ms-120 ms. > > Setup Configuration: > We are using ActiveMQ 5.2 on Sun Solaris 10 - SPARC JVM 1.6_16; > Topic has Non-Durable Consumer; =A0we use Non-Transactional, Non-Persiste= nt > Messages > > Client program is a WebApplication running on JBoss-JVM instance on serve= r > machine 1 > ActiveMQ is a standalone broker jvm running on server machine 2 > Server program is another backend application (not web-application) on > another Jboss-JVM instance on server machine2. > > > Can any one help in solving this problem ? > > Thanks > Kumar > > ----- > Thanks, > Kumar Ravella > -- > View this message in context: http://www.nabble.com/Publishing-to-Topic-i= s-very-slow-in-higher-loads-ActiveMQ5.2.-tp23538009p23538009.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > --=20 http://blog.garytully.com Open Source SOA http://FUSESource.com