On 21 May 2014 at 12:49:19, Thomas Kristensen (thomas.kristen...@uswitch.com) wrote: > > My understanding was that, if a handler threw and exception, > the message wouldn't be ack'ed, but be put back on the exchange. > That does not seem to happen, and when qos is 1, we seem to get stuck, > as we are holding one outstanding message.
See my earlier email. This is not an uncommon expectation. You can do it by handling all exceptions you want to retry on and re-queueing the message (with basic.nack). But that's not always a good idea so Langohr does not do this in ack-unless-exception. -- MK Software Engineer, Pivotal/RabbitMQ -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
