[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=13091447#comment-13091447 ] 

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

I've spent some time re-testing and re-visiting old logs, and what I recall is that most of my effort here was discovering a set of jars that pass all existing unit tests for as7x, eap6x, wf8/9, etc, and fixes this case for wildfly.  I do not believe a jar exists that both fixes the bugs for wf and successfully passes all previous unit tests for as7x. 

The jboss-as / wf backwards-compatibility tests in their project are pretty sparse, so while kabir indicated his new test for this usecase has passed using the wf9 jars against an as7.1.2 runtime, some of our other integration tests were failing with that combination. 

At the time of commit, I was unable to find a set of jars that fixes all existing integration tests AND this new big-file deployment case for the as7x runtime stream.  I finally settled on a set of jars that fixed all existing cases (since they are more important) even if ti leaves the big-deployment bug present for the as7x stream. 

Hope that helps. Not sure where we should document this. 

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