What about marking the column when the jms message has been succesfully send ? I.e. when receiving the DONE status. This could lead to duplicate of course. The other way would be to use XA transaction (and still mark the rows as processed).
Or you could store the timestamp in your DB if you carefuly control the threading of the component. On 5/14/07, Alex_ynr <[EMAIL PROTECTED]> wrote:
This might be a silly question but here it goes. Apologies if it's something quite simple.... I'm using a DB polling class that extends PollingComponent support. It's nothing fancy, it just sends an <sql>...</sql> message to the JDBC component every few seconds.... Upon initialization the query is sth like "SELECT * FROM... WHERE timestamp=0; Then timestamp is set to the current timestamp and a few seconds later a new query is sent with timestamp= the previous timestamp... The results of the queries are published to JMS using JDBC component. Since i can persist those results in JMS, how can I persist teh state of the Polling component (i.e. the timestamp) so if there is a failure it picks up where it left off? -- View this message in context: http://www.nabble.com/PollinComponentSupport-Persistence-tf3754701s12049.html#a10611452 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
