Hi Önder, I think it might be worth looking into idempotent consumer pattern[1], or roll your own logic based on not committing the transaction that updates the status to 1 until finished and locking the row beforehand, and some databases (Oracle IIRC) have a SKIP LOCKED clause that you can use to fetch all unlocked rows.
So in pseudo code: SELECT FOR UPDATE ... WHERE STATUS = 0 SKIP LOCKED do work UPDATE ... SET STATUS = 1 WHERE ... COMMIT But yeah, I would rely on the database functionality to keep track of the status, I don't think shutdown strategy would be as helpful with SIGKILL, as the whole JVM would be forced to quit, zoran [1] https://camel.apache.org/idempotent-consumer.html On Thu, Jul 27, 2017 at 6:43 AM, onders <ondersezgin+camelu...@gmail.com> wrote: > Hi, > > As per my understanding, shutdown strategy is set per camelcontext. > Is there a way / other ways where we can apply shutdown strategy or custom > shutdown implementation per route(s) in a camel context? > > In my use case, i have number of events stored in database already. In order > to avoid reprocessing a single event multiple times, i use onConsume option > in sql component and mark their status e.g status=1 meaning 'processing' > where initially records were in the db with status=0 meaning 'initial'. What > i want to do is that when the PID of my camel context and routes is signaled > like 'kill -9 <pid>', i want to reset the status of records back to status=0 > 'initial' in order not to miss processing those records when the process is > restarted. > > Or is there any other way doing what i want to achieve? -- Zoran Regvart
