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

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on JBIDE-19641:
------------------------------------------

[~kabirkhan] I'm not sure what problem your recent comments are addressing. My impression was the WFLY-669 fix (https://github.com/emuckenhuber/wildfly/commit/03b0c954143bb61064c6095c6dfcf40a1e97c2f8) avoids the issue with InputStreamEntry.InMemoryEntry, at least for the call paths JBDS is using.

Oh, I see. Your test wasn't using the call path JBDS does. Yes, if you pass in an InputStream to the DeploymentPlan it needs to read the whole thing to determine the size. We should improve that but AFAIK that doesn't impact JBDS.

The chunking algorithm I used for sending response streams to the client is smarter. If we can use that while remaining compatible with older servers that would be better. Another option is the unused InputStreamEntry.CachingStreamEntry. Copying to disk makes me vaguely uncomfortable though.

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