[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Kabir Khan commented on JBIDE-19641:
------------------------------------
I am working on a test, and it deploys a 1GB jar against several old versions using the
current client. The status is
- AS 7.1.2 - FAILS
- AS 7.1.3 - FAILS
- AS 7.2.0 - PASSES
- EAP 6.2.0 - PASSES
- EAP 6.3.0 - PASSES
- EAP 6.4.0 - PASSES
Do we need to fix it for the 7.1.x releases? I should also add WF 8.0, 8.1 and 9 once
released to the test matrix. However this will need some work by Tomaz (currently on PTO)
to set it up on our CI first.
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)