Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 85569 invoked from network); 9 Apr 2009 16:37:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Apr 2009 16:37:36 -0000 Received: (qmail 2546 invoked by uid 500); 9 Apr 2009 16:37:35 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 2480 invoked by uid 500); 9 Apr 2009 16:37:35 -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 2470 invoked by uid 99); 9 Apr 2009 16:37:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2009 16:37:35 +0000 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 (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2009 16:37:27 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LrxFR-0004Kh-Bb for users@activemq.apache.org; Thu, 09 Apr 2009 09:37:05 -0700 Message-ID: <22974755.post@talk.nabble.com> Date: Thu, 9 Apr 2009 09:37:05 -0700 (PDT) From: Yaswanth To: users@activemq.apache.org Subject: Need inputs on options to be used for a high throughput request / response scenario MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: yaswanth.mtrx@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, We are working on an application that has a message throughput of 15000-35000 messages /sec. We need to send a request message with a unique Id and wait for response to this id from a different system. Below are few options we found as we browsed through the web. We need sub second response with reliability and performance. Also the systems are clustered on either side. System has to be up and running with minimum heap memory increase. Please let us know which of the below options would be best 1. Synchronous non-persistent message receive with timeout on a queue using JMS Correlation Id 2. Synchronous non-persistent message and non-durable subscriber using receive with timeout on a topic using JMS Correlation Id 3. Queue Requestor using non-persistent message 4. Topic Requestor using non-persistent message and non-durable subscriber 5. Temporary Queues 6. Async receive using message listener and selector. In this option we are not sure how we can implement timeout if response is not received within a particular time Looking forward for inputs on the same Thanks in advance Yaswanth -- View this message in context: http://www.nabble.com/Need-inputs-on-options-to-be-used-for-a-high-throughput-request---response-scenario-tp22974755p22974755.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.