activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Hubert (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3597) Enable RedeliveryPolicy to determine next delay independent of the consumer
Date Sat, 19 Nov 2011 14:33:51 GMT


Eric Hubert commented on AMQ-3597:

I now worked through AM-1853 and see that this one was actually about making the consumer
behavior during redeliveries configurable (blocking versus non-blocking) which is indeed an
expected configuration option. But this will be available only once 5.6 is released.

Personally in addition to this configuration option I had expected another configuration option
for the end user to decide at which place the redelivery process is initiated/controlled (broker
versus consumer) as the use cases may predetermine the more suitable approach. Using Camel
as described in AMQ-2710 can be either seen as a workaround for the solution implemented in
AMQ-1853 or as a workaround for a missing "native" support for broker-based redelivery/redispatch.

Last but no least I also have to agree that the theoretical workaround I described under my
initial option b) to somehow circumvent the missing broker-side delay in letting the consumer
perform the delay would be indeed an odd counter-intuitive mixture of broker and consumer
controlled redelivery and only a result of neither getting the one nor the other approach
to work.
> Enable RedeliveryPolicy to determine next delay independent of the consumer
> ---------------------------------------------------------------------------
>                 Key: AMQ-3597
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Eric Hubert
>            Assignee: Timothy Bish
>             Fix For: 5.6.0
> Currently the redelivery is bound to the consumer instance requiring the end user to
use the same message consumer instance. This is due to the fact that the redelivery delay
is computated based on the previous redelivery delay (stored with the consumer instance) and
not based on the redeliveryCount of the message.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message