-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR9
-
None
-
Regression
-
-
-
-
-
-
Description of problem:
Client is unable to connect to remote+http://localhost:9990 intermittently (the connection timed out).
Exception from client side is thrown after 5 - 20 seconds (eg. 6995 ms, 8504 ms, 5023 ms, 7824 ms, 19223 ms, 5731 ms).
This issue is regression against EAP 7.0.0.
How reproducible:
30/1000030 times (0.002999910002699919%)
Steps to Reproduce:
CommandContext context = CommandContextFactory.getInstance().newCommandContext(); for (int i = 1; i <= requests; i++) { context.connectController(); context.disconnectController(); } context.terminateSession();
Actual results:
org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990 at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1352) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1143) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1120) at org.jboss.qa.repetitive.cli.test.CommandContextTestCase.lambda$testCommandContextConnection$2(CommandContextTestCase.java:107) at org.jboss.qa.repetitive.utils.TestExecution.test(TestExecution.java:64) at org.jboss.qa.repetitive.cli.test.CommandContextTestCase.testCommandContextConnection(CommandContextTestCase.java:110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1299) ... 33 more Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162) at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:180) at org.jboss.as.cli.impl.CLIModelControllerClient$3.getChannel(CLIModelControllerClient.java:132) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ... 35 more
Expected results:
No error.
- is cloned by
-
WFCORE-2151 Client is unable to connect to remote+http://localhost:9990 intermittently (the connection timed out)
- Resolved
- is incorporated by
-
JBEAP-8294 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta2
- Closed
- is related to
-
JBEAP-11888 (7.1.0) Connection timeout CLI issue on HTTPS, if more cli clients are used in a loop.
- Closed
- relates to
-
WFCORE-2241 Mem Leak in CLI class
- Resolved
-
JBEAP-11859 "WFLYPRT0060: Channel open request timed out" exception on CLI class
- Closed