[jbosstools-issues] [JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
Brian Stansberry (JIRA)
issues at jboss.org
Fri Jun 5 03:37:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13074516#comment-13074516 ]
Brian Stansberry commented on JBIDE-19641:
------------------------------------------
Progress report:
Adding this into the 7.2.0.Final code (which is quite close to the versions Rob reported), I don't get failures uploading to EAP 6.3. The file I used is 797MB.
I tested using an external IP address, not just localhost, but I'm traveling so I can't test against an actual remote server.
{code}
public class HugeDeploymentTestCase {
private static final String addr = System.getProperty("management.address", "localhost");
@Test
public void test() throws IOException, ExecutionException, InterruptedException {
ModelControllerClient client = ModelControllerClient.Factory.create(addr, 9999);
ServerDeploymentManager manager = ServerDeploymentManager.Factory.create(client);
File f = new File("/home/me/tmp/kitchensink-huge.ear");
Assert.assertTrue(f.exists());
DeploymentPlan plan = manager.newDeploymentPlan().add("kitchensink-huge.ear", f).build();
Future<ServerDeploymentPlanResult> future = manager.execute(plan);
ServerDeploymentPlanResult result = future.get();
}
}
{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)
More information about the jbosstools-issues
mailing list