We use Camel's jmx statistics to determine the health state. 1. if here has been an completed exchange within a given timeframe eg. 10 min. everything is ok. if the last exchange was a failure healthstate is set to error.
2. if no exchange has been completed a secondary check is activated. This is a custom resoucecheck eg. at ftp or file checker, that checkes that no unconsumed files exists. (they should have been consumed if the route was running ok). If unconsumed files exists an error is reported. The last one would catch your situation where your route suddenly stops consuming. You could have some kind of supervisor service running locally on the box, that on intervals checks all your routes and publishes health state to nagios. -- View this message in context: http://camel.465427.n5.nabble.com/Check-that-file-component-is-still-polling-tp5727333p5727426.html Sent from the Camel - Users mailing list archive at Nabble.com.
