We would like to use Camel to control the sending of HTTP requests to external services. Part of this effort is to resubmit error messages (target server crashes, public network failures, etc.). We can easily accomplish this (which is amazing!) By setting a retry policy on the error handler in our Camel route.
However, the exponential shipment delay that we would like to achieve ultimately far exceeds the acceptable graceful closing period. For deployment purposes, we want to shut down the service for a short period (~ 60 s). This leaves the possibility of re-pass messages.
Is there a way Camel can save current messages on shutdown and then load back after system startup? I watched, and it seems to us that we may have to implement our own InflightRepository and / or LifecycleStrategy, however I decided that it is better to ask before we begin with this seemingly involved way.
Thanks Kevin
source share