If you set the prefetchSize to 1 then you will only be given 1 message by your subscription so that you can ACK the message, then you'll be given another message etc.
http://incubator.apache.org/activemq/stomp.html e.g. add the following header activemq.prefetchSize: 1 More background here http://incubator.apache.org/activemq/what-is-the-prefetch-limit-for.html On 8/22/06, blueshed <[EMAIL PROTECTED]> wrote:
I have built an asynchronous stomp client that works well enough. I tried to introduce a synchronous stomp client but came across a problem: reciepts are sent out of order. When I send a SUBCRIBE I get a MESSAGE back before the RECEIPT - the MESSAGE requires an ACK before I get any more messages. The ACK too requests a RECEIPT and then two RECEIPTS come back. I would like my Stomp Client to work with Twisted Python and it is single threaded. I would like to work with messages in order with as little state as possible. Any thoughts? Could message consumption on the server complete the consumption before sending more messages? -- View this message in context: http://www.nabble.com/Stomp-Receipts-tf2145063.html#a5921824 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
