Hi all, I'm having the exact same problem as leNerd explains in the OP, except I'm enriching from a JMS queue instead of a FTP server. Basically, I want ALL the queued messages instead of just one.
What's the situation and the recommended solution with Camel now? If we go with Willem's idea of starting and stopping a Camel route, how long should we let it run? I think in my use case, we could have a few ten messages in the queue at the most. How should we schedule the route stopping -- with another quartz timer, or just sleep in the route starting thread, or something else? As background, the JMS queue is a temporary resend queue for messages which have been processed for their content successfully, but have failed to be sent over SOAP to another server (network interruptions etc). We store them in the JMS queue and periodically attempt to resend (all of) them. Thanks, Lunchbox -- View this message in context: http://camel.465427.n5.nabble.com/Scheduled-Polling-Consumer-on-FTP-endpoint-tp472602p4574353.html Sent from the Camel - Users mailing list archive at Nabble.com.
