activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (AMQ-1853) Optional non-blocking redelivery
Date Thu, 28 Jul 2011 07:56:10 GMT


Claus Ibsen commented on AMQ-1853:

I said it was a side note, to tell that async redeliver is possible using the technique with
a scheduled task. Not that it will resolve your issue. The problem is the AMQ broker, and
Camel cannot magically resolve that issue.

And beside Camel supports a threads in the DSL so you can hand over the message to another
thread to continue routing that message. By which the consumer thread can pickup the next

> Optional non-blocking redelivery
> --------------------------------
>                 Key: AMQ-1853
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Demian Mrakovich
>             Fix For: 5.6.0
> When a message is redelivered the consumer blocks for the amount of time specified by
the redelivery delay. For a high load scenario where message order is irrelevant this is just
reducing performance and will result in a complete halt if the delay is long and several bad
messages are consumed in a short time. 
> I think what I basically wish for is how it worked in versions 3.x, prior to fix for
AMQ-268. So I would very much like to have configurable option to NOT block consumers when
redelivering messages. 
> If no-one feels up to it, I'd still appreciate some hints and I could try to fix it myself.
Looking at ActiveMQMessageConsumer.rollback(), I was thinking something in the lines of just
scheduling a task to put the message back on queue after a delay - if configured to, instead
of stopping delivery and a schedule a task to resume delivery again. But I do not possess
an understanding of AMQ thorough enough to predict potential side effects of this, so any
analysis would be helpful.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message