activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farhad Dehghani (JIRA)" <>
Subject [jira] [Commented] (AMQ-1853) Optional non-blocking redelivery
Date Wed, 27 Jul 2011 14:23:10 GMT


Farhad Dehghani commented on AMQ-1853:

I can't believe that you refuse to fix this issue after being around for such a long time.
The fix represented in the is too simplistic
and cannot be applied in complex systems. There are workarounds for sure, but shouldn't be
necessary. On the other hand this blocking behavior of redelivery mechanism makes using the
RedeliveryPolicy somewhat irrelevant.
The blocking/non-blocking behavior should definitely be made optional. Not fixing it would
be admission to failure.

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