[jboss-jira] [JBoss JIRA] (WFLY-4373) WildFly CLI API ModelControllerClient memory leak?
Georgy Go (JIRA)
issues at jboss.org
Wed Apr 8 06:37:20 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056872#comment-13056872 ]
Georgy Go commented on WFLY-4373:
---------------------------------
Yes it still happen, the threaddump is attached to the issue now (i tested this in webapp, so the only server dump there). I've called this snippet in test app for 3 times: two times it was succeed, last one got frozen.
Seems to be I setted the title to <memory leak> up mistakenly. In this way I would to hightlight the threat of not closed session's overlay.
XNIO libraries are standart one, it's from maven repository, as suggested to use by WildFly documentation.
Worth to note, priority of the bug could take lower because the client can be opened once per app's lifetime, and it's incorrect closing can be handled by GarbageCollector.
> WildFly CLI API ModelControllerClient memory leak?
> --------------------------------------------------
>
> Key: WFLY-4373
> URL: https://issues.jboss.org/browse/WFLY-4373
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, IO
> Affects Versions: 8.2.0.Final
> Environment: Ubuntu 14.04 LTS, Java 1.8, xnio-api and xnio-nio are 3.3.0.Final
> Reporter: Georgy Go
> Assignee: Tomaz Cerar
> Labels: cli, dmr
> Attachments: threaddump.zip
>
>
> The following snippet of code to redeploy an application:
> ModelControllerClient cl = ModelControllerClient.Factory.create("localhost", 9999);
> ModelNode operation = new ModelNode();
> operation.get("operation").set("redeploy");
> operation.get("address").add("deployment", "server.war");
> cl.execute(operation);
> cl.close();
> - works fine, but .close() freezes forever.
> This issue depends to not only redeploy, but also for any other operations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list