Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Mon, 8 Apr 2013 16:17:18 +0000 (UTC)
From: "Lahiru Gunathilake (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12543393.1329768155355.128070.1365437838704@arcas>
In-Reply-To: <JIRA.12543393.1329768155355@arcas>
References: <JIRA.12543393.1329768155355@arcas>
Subject: [jira] [Resolved] (AIRAVATA-316) Provide a way to access the log
 for each experiment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AIRAVATA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AIRAVATA-316.
-----------------------------------------

    Resolution: Fixed
    
> Provide a way to access the log for each experiment 
> ----------------------------------------------------
>
>                 Key: AIRAVATA-316
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-316
>             Project: Airavata
>          Issue Type: New Feature
>    Affects Versions: 0.3-INCUBATING
>         Environment: mac
>            Reporter: Lahiru Gunathilake
>             Fix For: 0.7
>
>
> Provide a mechanism for Gateway administrator to track down the logs of each invocation easily without looking in to the big log file which contains all the logging information when you deploy the airavata system on tomcat. This will help Gateway admin to track down the error when somethings goes wrong. Its true that XBaya will save the Errors in to registry and its possible to retrieve error if there are any, but still accessing log separately for each inovation is a valid requirement.
> Lahiru

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira