continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent N Atkinson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONTINUUM-2746) Running build reports for a large number of builds can crash continuum
Date Sat, 02 May 2015 21:49:06 GMT

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

Brent N Atkinson commented on CONTINUUM-2746:
---------------------------------------------

It appears that the CSV export suffers from a slightly different problem that causes a similar
outcome. Due to using the struts StreamResult with an in-memory Stream for CSV, a large CSV
export will cause an OOME. Additionally, the struts stream result flow forces you to build
the entire file before anything is streamed back to the browser.

So that we can truly stream efficiently, we should write the CSV output to the response as
soon as it is available. This also protects us from large content since we only have to allocate
server resources to a single unit of the output, and not the entire contents.

> Running build reports for a large number of builds can crash continuum
> ----------------------------------------------------------------------
>
>                 Key: CONTINUUM-2746
>                 URL: https://issues.apache.org/jira/browse/CONTINUUM-2746
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Brent N Atkinson
>            Assignee: Brent N Atkinson
>              Labels: maybe-1.5
>             Fix For: 1.5.0
>
>
> This needs to be investigated further, but it appears that it may be possible to crash
continuum when running a build report for ALL reports when the number of builds is large.
Allowing unbounded queries like this should be prevented.



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

Mime
View raw message