Hi Michael,

Once again, thanks for all the explanation. I've experimented a bit this
morning, and I've isolated what I find weird.

If you run

https://github.com/tgk/langohr-consumer-dies-spike/blob/master/src/spike.clj

you'll notice that the message gets rejected as we'd expect when the
exception is NOT re-thrown, but the reject seems to be ignored in the case
where we re-throw. You could argue that you should never have a handler
throw exceptions to the langohr-lib, but seeing as this can happen, and
since it handles exceptions just fine when :auto-ack is true (not
demonstrated in the experiment, but tested and verified), it seems that a
consistent behaviour on a reject should be to continue consuming.

Is there something I'm missing?

Once again, thanks for all the help.

Thomas


On 21 May 2014 09:54, Michael Klishin <mklis...@gopivotal.com> wrote:

> 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
>

-- 
*uSwitch is a trading name of uSwitch Ltd. Registered in **England and 
Wales **(Company No. 03612689). Registered Address: **Notcutt House, 36 
Southwark Bridge Road, London, SE1 9EU*

*This communication and any attachments contains information which is 
confidential and may be subject to legal privilege. It is for intended 
recipients only. If you are not the intended recipient you must not copy, 
distribute, publish, rely on or otherwise use it without our consent. Some 
of our communications may contain confidential information which it could 
be a criminal offence for you to disclose or use without authority. If you 
have received this email in error please notify the sender immediately and 
delete the email from your computer.*

*uSwitch Ltd reserves the right to monitor all email communications for 
compliance with legal, regulatory and professional standards.*

-- 
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.

Reply via email to