activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <>
Subject Re: STOMP order of acks?
Date Thu, 17 Dec 2009 09:53:05 GMT

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 (

Dejan Bosanac -

Open Source Integration -
ActiveMQ in Action -
Blog -

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?

View raw message