[jbosstools-issues] [JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

[Kabir Khan (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13077133#comment-13077133 ] 

Kabir Khan commented on JBIDE-19641:
------------------------------------

Actually they all pass, the issue was that the deployment upload was timing out on 7.1.x. The initial value for the timeout was 20s, and that works fine for >= 7.2.0. Bumping the value from 20s helps, and deploying the 1GB on 7.1.3 takes 6.5 minutes. So it seems something in the 7.1.x protocol handling is slower than what we have in later releases.

I've tried running this on the CI but get OOMEs, so we need a job with higher java memory settings (and possibly some dedicated agents allowing those higher settings).



> Big war deployment via management API gets stuck
> ------------------------------------------------
>
>                 Key: JBIDE-19641
>                 URL: https://issues.jboss.org/browse/JBIDE-19641
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.3.0.Alpha2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.Beta2
>
>         Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)