[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-19641:
---------------------------------------
[~rob.stryker], so it seems your jars are from EAP 6.1.0.Beta.
Last time I tried it (and it failed) I was deploying the big war to EAP 6.4 from JBDS
8.1.
So I tried the following:
1. Export big war in JBDS 8.1
2. Start EAP 6.4
3. Deploy big war using jboss-cli from EAP 6.4 - all OK
4. Undeploy
5. Deploy big war using jboss-cli from EAP 6.1 Beta - all OK
By "all OK" I mean the deploy command was finished, the server log said the war
is deployed and I even tried to download the included big file (JBDS installer) from the
browser and it worked (and md5 matched).
I was kind of hoping it would fail with the older jboss-cli :-\
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)