Hi, thanks for the answer. In this case I'll just ignore the error.
Regards, Markus Am 2012-01-11 16:25, schrieb [email protected]: > Thanks for reporting this bug. > > I have recorded this as http://www.mygrid.org.uk/dev/issues/browse/T2-2025 > > I have also verified that this log message can be ignored, as > provenance is still captured and kept separate for each of the nested > workflows with the same identifier. Export both to OPM and Janus, in > addition clicking on the individual processes within the nested > workflow works fine in the workbench. > > The error occurs at an early stage when the provenance records the > fact that a workflow ID was run - second time we already know that > (but fails to check for this already existing in the database), and so > the second call failing does not affect anything else. > > The error is logged both in the workbench and in the command line - > but is of course more obvious in the command line. > > > You can ignore this (and similar errors) from the provenance system by > adding a magic line to log4j.properties - let me know if you need > this. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
