taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stian Soiland-Reyes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAVERNA-884) Avoid debug messages from executeworkflow
Date Tue, 19 Jan 2016 14:54:39 GMT

    [ https://issues.apache.org/jira/browse/TAVERNA-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106826#comment-15106826
] 

Stian Soiland-Reyes commented on TAVERNA-884:
---------------------------------------------

I raised this bug as historically users have become concerned of any such outputs, even if
we know they are "harmless" it might look like if something is wrong with the workflow.

> Avoid debug messages from executeworkflow
> -----------------------------------------
>
>                 Key: TAVERNA-884
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-884
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Commandline
>            Reporter: Stian Soiland-Reyes
>              Labels: logging
>
> The below are debug messages that should be removed. They might come from different parts
of the code of taverna-commandline and taverna-engine
> {code}
>  sh executeworkflow.sh  examples/helloworld.wfbundle
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=400m; support was removed
in 8.0
> log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable to a "org.apache.log4j.Appender"
variable.
> log4j:ERROR The class "org.apache.log4j.Appender" was loaded by 
> log4j:ERROR [org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@7486b455[log4j:1.2.17(id=43)]]
whereas object of type 
> log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by [sun.misc.Launcher$AppClassLoader@677327b6].
> log4j:ERROR Could not instantiate appender named "CONSOLE".
> log4j:WARN No appenders could be found for logger (org.springframework.osgi.extender.internal.boot.ChainActivator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> Bundle: /tmp/robundle2801827278992542627/robundle.zip
> Outputs will be saved to the directory: /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-product/target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT/Hello_World_output
> Workflow Run Bundle: /tmp/robundle2801827278992542627/robundle.zip
> ERROR 2016-01-19 14:43:31,071 (org.apache.jena.riot:84) - [line: 1, col: 1 ] Content
is not allowed in prolog.
> Workflow completed.
> {code}
> This should be reduced to:
> {code}
>  sh executeworkflow.sh  examples/helloworld.wfbundle
> Outputs will be saved to the directory: /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-product/target/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT-dev/apache-taverna-commandline-3.1.0-incubating-SNAPSHOT/Hello_World_output
> Workflow completed.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message