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

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

The latest commit on https://github.com/wildfly/wildfly-core/pull/804 contains what I was trying to explain above, with this the test passes http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=56881&buildTypeId=WildFlyCore_ClientOldServerLinux&tab=buildLog. I am trying a run with more normal maven settings as well at http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=56887&tab=buildResultsDiv&buildTypeId=WildFlyCore_ClientOldServerLinux . I'll take a look at how that went in the morning.

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