[jboss-jira] [JBoss JIRA] (WFCORE-1712) CLIScriptSupportTestCase fails on pure-IPv6 machines
Brian Stansberry (JIRA)
issues at jboss.org
Thu Aug 11 15:36:01 EDT 2016
[ https://issues.jboss.org/browse/WFCORE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved JBEAP-5611 to WFCORE-1712:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1712 (was: JBEAP-5611)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Affects Version/s: (was: 7.1.0.DR1)
> CLIScriptSupportTestCase fails on pure-IPv6 machines
> ----------------------------------------------------
>
> Key: WFCORE-1712
> URL: https://issues.jboss.org/browse/WFCORE-1712
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> org.jboss.as.test.manualmode.management.cli.CLIScriptSupportTestCase#testConnectStatus fails on pure-IPv6 machines
> *How reproducible:*
> 100%
> *Steps to Reproduce:*
> # export PROXY_PARAMS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128 -Dhttp.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -Dhttps.proxyPort=3128"
> # mvn install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dipv6 $PROXY_PARAMS -Dtest=CLIScriptSupportTestCase -Dts.manualmode -DfailIfNoTests=false
> *Actual results:*
> Stacktrace:
> {noformat}java.lang.IllegalStateException: Unable to connect to controller.
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:294)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:276)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:393)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:381)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:83)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:114)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:218)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:179)
> at org.jboss.as.cli.impl.CLIModelControllerClient$3.getChannel(CLIModelControllerClient.java:138)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> 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:1157)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1003)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:980)
> at org.jboss.as.cli.scriptsupport.CLI.doConnect(CLI.java:278)
> at org.jboss.as.cli.scriptsupport.CLI.connect(CLI.java:82)
> at org.jboss.as.test.manualmode.management.cli.CLIScriptSupportTestCase.testConnectStatus(CLIScriptSupportTestCase.java:87)
> Standard Output
> Standard Error
> 5.6 sec
> {noformat}
> Test output:
> {noformat}[0m09:15:56,815 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final-redhat-1
> [0m[0m09:15:57,137 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
> [0m[0m09:15:57,331 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" starting
> [0m[33m09:16:00,230 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /mnt/hudson_workspace/eap-7x-as-testsuite-test-core-rhel-ipv6-CLIScriptSupport/49bf0d07/testsuite/manualmode/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [0m[0m09:16:00,413 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" started in 3532ms - Started 37 of 46 services (17 services are lazy, passive or on-demand)
> [0m09:16:00,477 INFO [org.jboss.as.cli.CommandContext] (main) Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
> [0m09:16:00,699 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" stopped in 86ms
> [0m[0m09:16:00,715 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" starting
> [0m[0m09:16:00,943 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> [0m[0m09:16:01,083 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
> [0m[0m09:16:01,143 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
> [0m[33m09:16:01,438 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /mnt/hudson_workspace/eap-7x-as-testsuite-test-core-rhel-ipv6-CLIScriptSupport/49bf0d07/testsuite/manualmode/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [0m[0m09:16:01,505 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.21.Final-redhat-1
> [0m[33m09:16:01,753 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-1) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
> [0m[0m09:16:01,944 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> [0m[0m09:16:01,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> [0m[0m09:16:01,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" started in 1221ms - Started 59 of 62 services (20 services are lazy, passive or on-demand)
> [0m[0m09:16:02,188 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Core 2.2.0.CR7-redhat-1 "Kenny" stopped in 55ms
> {noformat}
> *Expected results:*
> No errors
> *Additional info:*
> Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-Testsuite/view/EAP7-AS-Testsuite-Reproducers/job/eap-7x-as-testsuite-test-core-rhel-ipv6-CLIScriptSupport/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list