[jira] Created: (CARGO-595) Deployment fails if deployable too big (>35 MB)

Deployment fails if deployable too big (>35 MB)
-----------------------------------------------

                 Key: CARGO-595
                 URL: http://jira.codehaus.org/browse/CARGO-595
             Project: Cargo
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0
            Reporter: Savas Ali Tokmen


When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:

[INFO] [cargo:deploy]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Deployment error
Java heap space
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Deployment error
        at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
        at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
        at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
        at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/CARGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145538#action_145538 ]

Savas Ali Tokmen commented on CARGO-595:
----------------------------------------

This bug has two potential reasons:

1. The VM on which the CARGO plug-in is running is out of memory
2. The VM on which the server is running is out of memory

To fix is, add the -Xmx512m option to the environment variables CARGO and/or your server uses (for example, MAVEN uses MAVEN_OPTS).

You may allow less or more than the 512 MBs I've given as example. Also note that -Xmx is a MAXIMAL size, it doesn't mean the VM will occupy 512 MBs when launched with that option.

> Deployment fails if deployable too big (>35 MB)
> -----------------------------------------------
>
>                 Key: CARGO-595
>                 URL: http://jira.codehaus.org/browse/CARGO-595
>             Project: Cargo
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: Savas Ali Tokmen
>
> When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Deployment error
> Java heap space
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Deployment error
>         at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/CARGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145539#action_145539 ]

Savas Ali Tokmen commented on CARGO-595:
----------------------------------------

Another workaround observed is to use BEA JRockit 5.0 (we've tried with update 12). The problem doesn't seem to occur even with much bigger EARs (perhaps BEA allows more memory by default?)

> Deployment fails if deployable too big (>35 MB)
> -----------------------------------------------
>
>                 Key: CARGO-595
>                 URL: http://jira.codehaus.org/browse/CARGO-595
>             Project: Cargo
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: Savas Ali Tokmen
>
> When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Deployment error
> Java heap space
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Deployment error
>         at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/CARGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145597#action_145597 ]

Matt Wringe commented on CARGO-595:
-----------------------------------

you can use cargo to set the jvm memory options.

How is this a bug with cargo?

> Deployment fails if deployable too big (>35 MB)
> -----------------------------------------------
>
>                 Key: CARGO-595
>                 URL: http://jira.codehaus.org/browse/CARGO-595
>             Project: Cargo
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: Savas Ali Tokmen
>
> When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Deployment error
> Java heap space
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Deployment error
>         at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/CARGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145636#action_145636 ]

Savas Ali Tokmen commented on CARGO-595:
----------------------------------------

This is a bug with CARGO as we need to extra VM options for CARGO (or whatever we use to access it -in my case it was Maven)... On the other hand, we cannot solve the bug on CARGO, we can only put it in the "known problems" list with the appropriate solution.

> Deployment fails if deployable too big (>35 MB)
> -----------------------------------------------
>
>                 Key: CARGO-595
>                 URL: http://jira.codehaus.org/browse/CARGO-595
>             Project: Cargo
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: Savas Ali Tokmen
>
> When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Deployment error
> Java heap space
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Deployment error
>         at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

     [ http://jira.codehaus.org/browse/CARGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Savas Ali Tokmen closed CARGO-595.
----------------------------------

    Resolution: Not A Bug

This is not a bug, just a VM "feature" one needs to know about.

> Deployment fails if deployable too big (>35 MB)
> -----------------------------------------------
>
>                 Key: CARGO-595
>                 URL: http://jira.codehaus.org/browse/CARGO-595
>             Project: Cargo
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>            Reporter: Savas Ali Tokmen
>
> When deploying an application using CARGO, a deployment error occurs if the file to deploy is big (more than about 30 or 35 MB). Here's the log:
> [INFO] [cargo:deploy]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Deployment error
> Java heap space
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Deployment error
>         at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:79)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:118)
>         at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:243)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email