[#TAV-156] EnactorInvocation.detachFromModel() might destroy workflow instances too soon. - myGrid

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 1.5
Fix Version/s: 1.5
Component/s: Taverna Core
Labels:
None

Description

org.embl.ebi.escience.scuflui.EnactorInvocation.detachFromModel() now invokes workflowInstance.destroy() in order to prevent memory leaks. But for provenance and other event listeners this is a problem since it may destroy the instance before it is consumed.

We thus need to find a safer method to prevent memory leaks than this.

Issue Links

Depends

This issue has dependent:
~~TAV-153~~ Error from workflow id = 0

This issue related to:
~~TAV-165~~ Several workflow instances created

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Stian Soiland-Reyes added a comment - 2006-11-07 12:09

now actually done by onDispose() - but the problem is still the same.

Show

Stian Soiland-Reyes added a comment - 2006-11-07 12:09 now actually done by onDispose() - but the problem is still the same.

Hide

Permalink

Stian Soiland-Reyes added a comment - 2006-11-08 09:27

Should be resolved now by introducing two new events: WorkflowToBeDestroyedEvent is sent as wfInstance.destroy() has been called, delaying the actual destruction until that event has been propagated out. After the real destroy, a WorkflowDestroyedEvent is sent.

Show

Stian Soiland-Reyes added a comment - 2006-11-08 09:27 Should be resolved now by introducing two new events: WorkflowToBeDestroyedEvent is sent as wfInstance.destroy() has been called, delaying the actual destruction until that event has been propagated out. After the real destroy, a WorkflowDestroyedEvent is sent.

People

Assignee:

Stian Soiland-Reyes

Reporter:

Daniele Turi

Vote (0)

Watch (0)

Dates

Created:

2006-09-14 18:29

Updated:

2006-11-08 09:27

Resolved:

2006-11-08 09:27