[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19641:
-------------------------------------
[~brian.stansberry] Your code differs slightly from whats in ours.
You have:
{code}
DeploymentPlan plan = manager.newDeploymentPlan().add("kitchensink-huge.ear",
f).build();
{code}
While we use the following signatures:
{code}
DeploymentPlanBuilder builder = manager.newDeploymentPlan().add(name,
file).andDeploy().build();
Or...
DeploymentPlanBuilder builder = manager.newDeploymentPlan().deploy(name).build();
{code}
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)