[jboss-jira] [JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase Failing Due To Native Protocol Issue
Darran Lofthouse created WFCORE-2068:
----------------------------------------
Summary: HTTPSConnectionWithCLITestCase Failing Due To Native Protocol Issue
Key: WFCORE-2068
URL: https://issues.jboss.org/browse/WFCORE-2068
Project: WildFly Core
Issue Type: Bug
Components: Remoting, Test Suite
Reporter: Darran Lofthouse
Assignee: Jean-Francois Denise
Priority: Blocker
Fix For: 3.0.0.Alpha14
The listed test case is failing during clean up with the following error: -
{noformat}
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 41.112 sec <<<
FAILURE! - in org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase
org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase Time elapsed: 7.089
sec <<< ERROR!
org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9999
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)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1299)
at
org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1143)
at
org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1120)
at
org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.reloadServer(HTTPSConnectionWithCLITestCase.java:175)
at
org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.resetTestConfiguration(HTTPSConnectionWithCLITestCase.java:162)
{noformat}
The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working
fine, the issue is with the native management interface used for test clean up.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)