[
https://issues.jboss.org/browse/WFCORE-1218?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky moved JBEAP-2395 to WFCORE-1218:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1218 (was: JBEAP-2395)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.0.0.GA)
Affects Version/s: (was: 7.0.0.ER2 (Beta))
Affects Testing: (was: Regression)
Connecting to controller via new CommandContext instance leak
threads
---------------------------------------------------------------------
Key: WFCORE-1218
URL:
https://issues.jboss.org/browse/WFCORE-1218
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Priority: Blocker
Connecting to a controller via a new CommandContext always [init a new
console|https://github.com/jbossas/wildfly-core-eap/commit/9083ca79b4e30a...]
which could lead into "OutOfMemoryError: unable to create new native thread" as
initBasicConsole() creates a pair of Aesh thread which are not cleaned up with
terminateSession().
{code:java}
import org.jboss.as.cli.scriptsupport.CLI;
CLI cli = CLI.newInstance();
for (int i = 1; i <= tries; i++) {
cli.connect();
cli.disconnect();
}
{code}
Reproducer waits for 10s after every 50 connections, that's where the steps on the
graph comes from:
!7.0.0.er2.png|thumbnail!
Regression against 7.0.0.ER1 and 6.4.x
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)