[#TAV-48] Enactment does not terminate when running from the command line - myGrid

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.4
Fix Version/s: None
Component/s: Taverna Core
Labels:
None
Environment:
tested on Linux both within the IDE and directly from the command line

Description

Once a workflow has been run and the results have been obtained, the program does not terminate without explicity adding a System.exit(0).
Seems that there are some threads left running. (I think these are event queue threads, and also one gets created when compiling the workflow).

Issue Links

This issue related to:
~~TAV-127~~ Thread leak of ScuflModel.NotifyThread
~~TAV-18~~ Long running workflows

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

June Finch added a comment - 2007-02-16 11:12

Stian - Please retest and confirm whether this is still an issue. (If not, please close)

Show

June Finch added a comment - 2007-02-16 11:12 Stian - Please retest and confirm whether this is still an issue. (If not, please close)

Hide

Permalink

Stian Soiland-Reyes added a comment - 2007-02-19 09:22

Yes, it's still an issue.. investigating with profiler.

Show

Stian Soiland-Reyes added a comment - 2007-02-19 09:22 Yes, it's still an issue.. investigating with profiler.

Hide

Permalink

Stian Soiland-Reyes added a comment - 2007-02-19 10:02

It's two NotifyThread, one WorkflowEventDispatcher$NotifyThread and one Freefluo Queue$ConsumerThread (or something very similar), in addition to a "Thread 9" that doens't seem to ever do anything, and I can't even record why it is created.

However, doing a System.exit() as the current executor does is OK for invoking from the command line, these threads are not actually performing any work, and in that case we are only running one workflow anyway.

This could be an issue for the ~~TAV-18~~ Long running workflow service though, so it might be re-visited at that time.

Show

Stian Soiland-Reyes added a comment - 2007-02-19 10:02 It's two NotifyThread, one WorkflowEventDispatcher$NotifyThread and one Freefluo Queue$ConsumerThread (or something very similar), in addition to a "Thread 9" that doens't seem to ever do anything, and I can't even record why it is created. However, doing a System.exit() as the current executor does is OK for invoking from the command line, these threads are not actually performing any work, and in that case we are only running one workflow anyway. This could be an issue for the ~~TAV-18~~ Long running workflow service though, so it might be re-visited at that time.

People

Assignee:

Stian Soiland-Reyes

Reporter:

Stuart Owen

Vote (0)

Watch (0)

Dates

Created:

2006-07-25 13:11

Updated:

2007-02-19 10:03

Resolved:

2007-02-19 10:02