brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Svetoslav Neykov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-364) OutOfMemoryError deploying to Softlayer
Date Fri, 14 Oct 2016 19:09:20 GMT

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

Svetoslav Neykov commented on BROOKLYN-364:
-------------------------------------------

I used to get this when loading the available images list, but only in special cases when
the the requested imageId was private. Something like this - don't remember exactly. It will
first download the public images list which is short. Then it will fall back to all shared
images which is huge so either SL will time out or Brooklyn will get OOME.

I think there was some work to fix this, so we don't download all images. So this problem
might be unrelated.

> OutOfMemoryError deploying to Softlayer
> ---------------------------------------
>
>                 Key: BROOKLYN-364
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-364
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
>            Priority: Critical
>
> When deploying to SoftLayer, one often gets {{OutOfMemoryError}} due to heap space. This
is more likely to happen with several concurrent apps, or with large blueprints.
> The workaround is to (substantially) increase the allocated memory (first checking that
the VM can support that amount of memory!). For example, set {{-Xmx=4G}}.



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

Mime
View raw message