Redelivery Strategy Question

[mhuisking_michael.c.huisking]

Due to the possibility of a target system being down for several hours, I have a redelivery policy on a dead letter channel error handler that looks like this:

     <bean id="dlcRedeliveryPolicy" class="org.apache.camel.processor.RedeliveryPolicy">
          <property name="delayPattern" value="1:60000;2:300000;3:3600000;4:7200000;5:14400000;6:43200000"></property>
          <property name="retryAttemptedLogLevel" value="ERROR"></property>
          <property name="asyncDelayedRedelivery" value="true"></property>
          <property name="maximumRedeliveries" value="6"></property>
     </bean>

Since there is a possibility for messages to be delayed for several hours, is there a way that I can protect these "in transit" messages in case of system failure (power outage, etc.)  I haven't looked at the way this is implemented, but I imagine that these messages are just stored in memory -- so, can I configure something for more reliability?

Thanks in advance,

Mick

Edited by: mhuisking on Jan 18, 2013 3:55 AM

Typo

[davsclaus]

No the Camel redelivery error handler is in-memory only.

[mhuisking_michael.c.huisking]

Thanks Claus,  a couple of last questions on this then.  Is there a way to get info on the "in flight" messages? (if someone decides to shut down while there are messages pending) I haven't tried the new JON monitoring, but is that one of the pieces of data exposed in the monitoring interface?

Thanks in advance,

Mick

[davsclaus]

There is an InflightRegistry API in the org.apache.camel.spi package. And you can get access to that from CamelContext. Then you can use that API to know how many current in-flight messages there is in total, or per route (started from that route).

[mhuisking_michael.c.huisking]

Thanks!

[davsclaus]

The Camel JMX MBeans will expose in flight counter for

- camel context mbean

- route mbean(s)

eg in-total and per individual route, eg as these mbean also uses that in-flight registry to get these numbers.