camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-7012) RedeliveryPolicy.redeliveryDelay is not functioning as expected
Date Wed, 27 Nov 2013 08:23:38 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-7012.
--------------------------------

       Resolution: Invalid
    Fix Version/s: 2.13.0
         Assignee: Claus Ibsen

Please use the mailing list / user forum to get help

You can read here about how to get help/support and what you can/should do:
http://camel.apache.org/support

> RedeliveryPolicy.redeliveryDelay is not functioning as expected
> ---------------------------------------------------------------
>
>                 Key: CAMEL-7012
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7012
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.11.0
>            Reporter: Vinod
>            Assignee: Claus Ibsen
>             Fix For: 2.13.0
>
>
> Please find the below configuration, that I tested. As per the below configuration retry
will happen after 90 seconds. But actually retry is happening after 210 seconds. That means
2 minute/120 second added without configuring/ without my knowledge.
>  
> <route id="1111" errorHandler="myDeadLetterChannel">
> ......
> <route>
> 	<bean id="myDeadLetterChannel" class="org.apache.camel.builder.DeadLetterChannelBuilder">
> 		<property  name="deadLetterUri"  value="activemq:queue:deadLetterChannel?exchangePattern=InOut&amp;replyTo=outgoing"/>
> 		<property  name="redeliveryPolicy" ref="myRedeliveryPolicy"/>
> 	</bean>
> 	<bean id="myRedeliveryPolicy" class="org.apache.camel.processor.RedeliveryPolicy">
>     		<property name="maximumRedeliveries" value="3"/>
>     		<property name="redeliveryDelay" value="90000"/>
> 	</bean>
> attached the logs
> [Nov 26 17:19:05:509] INFO  (CacheUriBuilder.java:18) - Start of CacheUriBuilder
> [Nov 26 17:19:05:545] INFO  (CacheUriBuilder.java:21) - Exchange body is : <clm-is-interface>
>         <interface>
>                 <api>xxxxx</api>
>                 <contextId>TXN141</contextId>
>         </interface>
> </clm-is-interface>
> [Nov 26 17:19:05:550] INFO  (CacheUriBuilder.java:27) - Cache context ID is : TXN141
> [Nov 26 17:19:05:550] INFO  (CamelUtils.java:45) - Start of setExchangeHeadersTypeGet()
method.
> [Nov 26 17:22:35:913] INFO  (CacheUriBuilder.java:18) - Start of CacheUriBuilder
> [Nov 26 17:22:35:914] INFO  (CacheUriBuilder.java:21) - Exchange body is : <clm-is-interface>
>         <interface>
>                 <api>xxxxx</api>
>                 <contextId>TXN141</contextId>
>         </interface>
> </clm-is-interface>
> [Nov 26 17:22:35:949] INFO  (CacheUriBuilder.java:27) - Cache context ID is : TXN141
> [Nov 26 17:22:35:950] INFO  (CamelUtils.java:61) - End of setExchangeHeadersTypeGet()
method.
> [Nov 26 17:22:35:951] INFO  (CacheUriBuilder.java:57) - End of CacheUriBuilder
> [Nov 26 17:26:06:342] INFO  (CacheUriBuilder.java:18) - Start of CacheUriBuilder
> [Nov 26 17:26:06:343] INFO  (CacheUriBuilder.java:21) - Exchange body is : <clm-is-interface>
>         <interface>
>                 <api>xxxxx</api>
>                 <contextId>TXN141</contextId>
>         </interface>
> </clm-is-interface>
> Please suggest any work around/ fix?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message