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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-19641:
-------------------------------------

I've got a topic branch I'm working on using wf9 cr2 jars in jbt for the 7.x / eap6x clients in our tools.  I've confirmed that using the wf9 cr2 jars, updating the timeout, and changing the heap, together, will allow the wf9 jars to work with jboss 7.1 (and i assume based on kabir's comments) that it would also work for all others.   My topic branch timeout on deploys for 7x is a linear scaling based on filesize of the target file to deploy... not sure if this is best or not, but it seems to work. 

So that's awesome.  I'll wait for the final the be released, re-test, and clean up the branch and provide it to martin for testing. 

> 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)