Return-Path: 
 <activemq-users-return-6651-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 82158 invoked from network); 15 Jan 2007 19:03:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Jan 2007 19:03:49 -0000
Received: (qmail 80489 invoked by uid 500); 15 Jan 2007 19:03:55 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 80476 invoked by uid 500); 15 Jan 2007 19:03:55 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 80467 invoked by uid 99); 15 Jan 2007 19:03:55 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 11:03:55 -0800
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 (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 11:03:45 -0800
Received: from [72.21.53.38] (helo=jubjub.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1H6X76-0001uV-Lo
	for activemq-users@geronimo.apache.org; Mon, 15 Jan 2007 11:03:24 -0800
Message-ID: <8376423.post@talk.nabble.com>
Date: Mon, 15 Jan 2007 11:03:24 -0800 (PST)
From: Paul French <paul.french@frenchiesystems.com>
To: activemq-users@geronimo.apache.org
Subject: Session.DUPS_OK_ACKNOWLEDGE
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: paul.french@frenchiesystems.com
X-Virus-Checked: Checked by ClamAV on apache.org


ActivemQ 4.1.0


Where do I set Session.DUPS_OK_ACKNOWLEDGE this? I'm trying to increase
performance of the messaging layer and I'm going through the performance
guide at 
http://devzone.logicblaze.com/site/apache-activemq-performance-tuning-guide.html
http://devzone.logicblaze.com/site/apache-activemq-performance-tuning-guide.html 

I can send out a 1000 messages a second no problem but the rest of the
messaging layer is very slow so I need some help here.

My scenario is client creates many messages and sends async to the broker
(one connection, one session). The client also creates a temporary queue to
receive replies on. The client also starts a number of consumers to listen
on the temp queue.

A consumer consumes the messages and then replies by placing a message on
the temporary queue.

My client receives the reply via the temp queue.


I have no need for Quality Of Service or persistence. So far for the cleint
I have set the following properties to improve performance:

  <bean id="connectionFactory"
class="org.springframework.jms.connection.SingleConnectionFactory">
    <property name="targetConnectionFactory">
      <bean class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL">
         
<value>tcp://192.168.160.86:61616?jms.prefetchPolicy.queuePrefetch=100</value>
        </property>
        <property name="useAsyncSend"><value>TRUE</value></property>
        <property name="optimizeAcknowledge"><value>TRUE</value></property>
      </bean>
    </property>
  </bean>

Is optimizeAcknowledge related to Session.DUPS_OK_ACKNOWLEDGE?

For the server side I have used the same properties for now:

  <bean id="connectionFactory"
class="org.springframework.jms.connection.SingleConnectionFactory">
    <property name="targetConnectionFactory">
      <bean class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL">
         
<value>tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=100</value>
        </property>
        <property name="useAsyncSend"><value>TRUE</value></property>
        <property name="optimizeAcknowledge"><value>TRUE</value></property>
      </bean>
    </property>
  </bean>


The server and broker run on the same machine for this test but will not in
production hence I have not bothered trying to embed the broker in the
server.

Baiscally for this test my client is punching out about 1000 messages and I
want to see how long it takes to get replies. At the moment I am pumping out
about 1000 messages in about 2 seconds but it takes 20 seconds to get the
1000 replies. I am obviously missing something here?? Any pointers would be
great.

I am using a laptop as my client and a big chunky solaris box as my server
all on the same local LAN.
-- 
View this message in context: http://www.nabble.com/Session.DUPS_OK_ACKNOWLEDGE-tf3016262.html#a8376423
Sent from the ActiveMQ - User mailing list archive at Nabble.com.