Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 74210 invoked from network); 6 Sep 2007 11:30:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Sep 2007 11:30:24 -0000 Received: (qmail 6713 invoked by uid 500); 6 Sep 2007 11:30:17 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 6668 invoked by uid 500); 6 Sep 2007 11:30:17 -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 6646 invoked by uid 99); 6 Sep 2007 11:30:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2007 04:30:17 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG 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, 06 Sep 2007 11:30:12 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1ITFYW-0008MJ-CG for users@activemq.apache.org; Thu, 06 Sep 2007 04:29:52 -0700 Message-ID: <12520552.post@talk.nabble.com> Date: Thu, 6 Sep 2007 04:29:52 -0700 (PDT) From: Juergen Mayrbaeurl To: users@activemq.apache.org Subject: Strict order of messages with redelivery MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: juergen.mayrbaeurl@hvb.sozvers.at X-Virus-Checked: Checked by ClamAV on apache.org Hi! Our application has to make sure that all consumers with durable topic subscriptions get messages in strict order even when a message has to be delivered. E.g. Publisher puts message 1 to 10 on topic. Consumer opens a session, gets message 1, makes a client acknowledment, gets message 2, makes a client acknowledment, and so on. On message 3 a runtime exception occurs and no client acknowledment is done, but the session and the connection are closed. The next time the consumer opens a session message 4 gets delivered before message 3. What do we have to do to get message 3 (and not 4) as the first message? Do we have to use a special redelivery policy? Kind regards Juergen PS: We're using ActiveMQ 4.1.0 -- View this message in context: http://www.nabble.com/Strict-order-of-messages-with-redelivery-tf4391491s2354.html#a12520552 Sent from the ActiveMQ - User mailing list archive at Nabble.com.