brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-364) OutOfMemoryError deploying to Softlayer
Date Mon, 21 Nov 2016 00:16:58 GMT

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

Aled Sage commented on BROOKLYN-364:
------------------------------------

This is fixed in jclouds 2.0.0, and will be fixed in the next jclouds 1.9.3 release.

> 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