On Thu, Nov 12, 2009 at 16:31, Stian Soiland-Reyes <[email protected]> wrote: > The issue is that some services like Biomart return values by > pipelining, and so they deliver outputs at indexes deeper than as the > job went down - and so there's no job to forget when the clearing goes > down the dispatch stack. This should not be a problem, and so I > changed the logging to debug.
This got quite techie if you are not a Vodoo Dispatch Stack Hacker. What happens is that something triggers the running of a service, and a job is sent down the dispatch stack at say index [3] with some inputs. The activity is then meant to return values at [3]. As the BioMart does pipelining (streaming the returned data), it will return individual items of the list that should be returned at [3], so it will return: [3,0] [3,1] [3,2] (..) [3] (all of the above registered) So in addition to the expected [3] it will deliver the individual items, but there was never requested for a job [3,1], so layers like Retry get slightly confused as there's no internal state (like number of retries for [3]) to delete for [3,1] - hence the initial log message. As this is not dangerous in this case, but rather expected, I've made the log message debug instead of warning. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
