Hi! I've noticed that simply by loading a workflow I get loads of "ErrorBounce layer state cleanup" threads running.
It seems that a new timer is started for each dispatch layer for each processor for each workflow. These timers seems to only be active at running a workflow - and they don't seem to be destroyed in any way. This means we've introduced a thread leak depending on the number of workflow openings and runs (as running makes a copy of the workflow). I'll be changing these to use a single, static timer in the parent class as I don't think this should make it for the 2.1 Beta. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ taverna-hackers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-hackers Developers Guide: http://www.mygrid.org.uk/usermanual1.7/dev_guide.html FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
