Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 82534 invoked from network); 17 Dec 2009 09:53:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Dec 2009 09:53:29 -0000 Received: (qmail 67529 invoked by uid 500); 17 Dec 2009 09:53:28 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 67481 invoked by uid 500); 17 Dec 2009 09:53:28 -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 67471 invoked by uid 99); 17 Dec 2009 09:53:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 09:53:28 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chubrilo@gmail.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-vw0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 09:53:26 +0000 Received: by vws7 with SMTP id 7so549532vws.22 for ; Thu, 17 Dec 2009 01:53:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=5YnmrixAxAUFHtB5SOZa3TDtXBrrN3/iDGzfi5qU8eA=; b=PGweelJRhZKnIzfVGMtV55MBaguCojrIGltJgjPK5JE1oTxDIA9c9lWMS7h6MC9Acz dWLxlCGDt30q/W7PTkJv9/ak6Lighh79Gzh8VIdenOcgfi3z95R3/hcVYQR340GcftmY aN6R+3H0gYJBZ04BswT0w09JB0JGbnPaAibEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ocfiORoj2O/eUL8vbCkwJfV8Dz/P0AjVpV6ZO3JfKi+3CJpSXBXNmOpL4lHNFkxcbS NVW2Y0QDaZjLBnIrw6ZhZfb8Hh4hAEhJa+yxKG7vawrDaS5dL2OqGYNTwp/U3OSU+PAO o5mgb4e7WDxGP6R09SUDFr2j59sVSgEJI+tTM= MIME-Version: 1.0 Sender: chubrilo@gmail.com Received: by 10.220.124.68 with SMTP id t4mr549084vcr.35.1261043585146; Thu, 17 Dec 2009 01:53:05 -0800 (PST) In-Reply-To: References: Date: Thu, 17 Dec 2009 10:53:05 +0100 X-Google-Sender-Auth: 0fd50807f44588b9 Message-ID: <36e91d9d0912170153g179464d1n183df8e445206417@mail.gmail.com> Subject: Re: STOMP order of acks? From: Dejan Bosanac To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, it's not a but. With client ack, the ack you send will acknowledge all message up to the one you're sending ack for. So if you send acks out of order, you'll get "unexpected ack" message. You can use client-individual ack to achieve your desired functionality (http://issues.apache.org/activemq/browse/AMQ-1874) Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Thu, Dec 17, 2009 at 10:25 AM, Aleksandar Ivanisevic wrote: > > Hi, > > I have a consumer with prefetch>1 and client ack. If I send the acks > out of order (not in the order the messages are received), I get an > exception: > > org.apache.activemq.transport.stomp.ProtocolException: Unexpected ACK received for message-id > > is this in JMS specification that acks need to be received in the same > order or is it STOMP bug? > > If it is supposed to be like that, how is one supposed to handle > messages in parallel? Have a separate consumer for each thread? > > Hm, just found out that when I get this exception the message never > gets redelivered, so this must be a STOMP bug, right? > > >