airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-437) Stdout and stderr files are read as string and will be problem if the file are big
Date Wed, 30 Jul 2014 22:37:39 GMT

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

Suresh Marru resolved AIRAVATA-437.
-----------------------------------

    Resolution: Won't Fix

Since the issue is a concern on tomcat deployment, resolving for now. But the problem might
exist neverthless. I suggets revisting this issue on a latest release and create a new jira
with latest observations.

> Stdout and stderr files are read as string and will be problem if the file are big
> ----------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-437
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-437
>             Project: Airavata
>          Issue Type: Bug
>          Components: GFac
>    Affects Versions: 0.4-INCUBATING
>            Reporter: Raminderjeet Singh
>              Labels: Contributor
>             Fix For: 0.13
>
>
> Currently Stdout and stderr files are read as String to be evaluated against regex to
get output paramameters. These files can grow big and gfac may run into out of memory. With
the new infrastructure with all the services hosted on same tomcat/axis2 server (may not be
recommended but how its currently), we need to be more careful about memory usage. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message