[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on JBIDE-19641:
------------------------------------------
Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE
is using is the same once it reaches the point where the bits are being pushed to the
server (which is where things are stuck.) But it turns out that's not the case; the
management op the CLI uses is different.
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.Beta1
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)