Hi all. I have a problem regarding changing the timer period on the fly. My concrete problem is that I have around 1.200.000 historic records I need to extract at one time, and the database table is updated every 24 hours. Furthermore I'm extracting from a Microsoft SQL database.
My preliminary tests have shown that I can't retrieve more than 3000 rows at a time. All this means that I would like to create a route that starts out by extracting 3000 rows, at a time, as fast a possible. When all the 1.200.000 historic records have been extracted, the timer period should be changed to only "fire" every 24 hours. I have been looking into the throttler component, but I'm not sure that one will work. The reason for this is that it will only be in a very short time, that I want to poll as fast as possible, and after that I will only poll every 24 hours for eternity. Furthermore, I can't figure out how the throttler component know when to hold back. As I understand, the throttler is controlled by how many exchanges that are going on right now, and therefore only relates to the internal part of Camel. This means that the throttler doesn't care about me only wanting data from a remote place every 24 hours. Best regards Lasse Vestergaard -- View this message in context: http://camel.465427.n5.nabble.com/Change-timer-runtime-tp5738484.html Sent from the Camel - Users mailing list archive at Nabble.com.
