#015325: Execution state should be stored atomically

Description:

The execution state is only commited by ezcWorkflowDatabaseExecution when it is suspended or ended, and not after an individual node finished executing.

If at any time after starting or resuming an execution the system encounters an unhandled exception or a fatal error all state of the current execution is lost.


Environment:

Operating System:
PHP Version: (please be specific, like '4.4.3' or '5.1.5')
Database and version:
Browser (and version):


- Attachments

No attachments for this issue.


- Comments

When a workflow execution is resumed, the state of the execution will not be updated in the database immediately anymore.

#262841 by Sebastian Bergmann on August 29th, 2009 [Permanent Link]

- History
Load History
Properties
Type Enhancement
Priority Medium
Component Components » WorkflowDatabaseTiein
Affects Unknown
Fix Versions 2009.2 sprint 2 - eZ components 2009.2 sprint 2
2009.2alpha1 - eZ components 2009.2alpha1
Reporter Sebastian Bergmann
Responsible Sebastian Bergmann
Status 0 Closed
Resolution Implemented
Created August 19th, 2009
Updated August 29th, 2009
Resolved August 29th, 2009
 
Navigation [Permanent Link]
Previous Issue
Back to Issues List
Next Issue: #015537
  Graph shows to small and truncated rotated axis labels