Making task management persistent/transactional
-----------------------------------------------
Key: ESBJAVA-539
URL: https://wso2.org/jira/browse/ESBJAVA-539
Project: WSO2 ESB
Issue Type: Improvement
Components: Core Engine
Affects Versions: 1.7
Reporter: Paul Fremantle
Assignee: Asankha Perera
Suppose we have a task defined to run every day at 12:30. What if the system is
down at that point? We may still want the task to run at 12:35 when the system
starts.
Secondly, what if the system fails during running a task. The work should be
rolled back and the task re-run.
Of course, there are many situations where this isn't true as well. If I am
polling a system every 5 seconds, it may not matter. In fact, I probably do not
want extra polling to happen when the system restarts. So this needs to be
optional. Quartz has got a persistent model, so I'm sure this is already
thought of by the Quartz team, but when we integrated into Synapse/ESB we
didn't look at those aspects yet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
