[ 
https://issues.apache.org/activemq/browse/AMQ-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59061#action_59061
 ] 

Gary Tully commented on AMQ-2710:
---------------------------------

resolved in r937289

The IdentityMessageReuseConverter allows the in message to be reused as is, for 
the transfer. The AMQ_SCHEDULED_DELAY header tells the broker to delay delivery 
by 30 seconds.
Example route:{code} <bean id="messageConverter" 
class="org.apache.activemq.camel.converter.IdentityMessageReuseConverter" />
  <camelContext xmlns="http://camel.apache.org/schema/spring"; trace="true">
    <route>
      <setHeader 
headerName="CamelRedeliveryMarker"><constant>true</constant></setHeader>
      <setHeader 
headerName="AMQ_SCHEDULED_DELAY"><constant>30000</constant></setHeader>
      <to pattern="InOnly" 
uri="activemq:camelRedeliveryQ?explicitQosEnabled=true&amp;messageConverter=#messageConverter"/>
    </route>
  </camelContext>

{code}

> Validate camel route to pull from DLQ and reroute to destination after a delay
> ------------------------------------------------------------------------------
>
>                 Key: AMQ-2710
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2710
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Test Cases
>    Affects Versions: 5.3.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> Redelivery attempts pile up in the activemq RA and block a consumer in pure 
> jms. A strategy where messag order is ignored and messages are rerouted to 
> the original destination after some period can allow the broker to deal with 
> the redelivery and allow the application to continue with valid messages 
> while the remaining ones are pending.
> Using a no retry delivery policy and an individual DLQ policy allows 
> redeliveries to be diverted to the DLQ immediately. Adding in a camel route 
> that takes from the DLQ and schedules a delayed delivery to the original 
> destination provided a clean alternative, at the cost of breaking queue order 
> semantics for the pure JMS case.
> An example of such a camel route would be nice.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to