Running Tests on a real remote Wildfly-10

I tried to execute a test on a remote Wildfly container. Only getting a strange message: “No result returned”. I verified that the test get executed on the remote machine. It looks like some protocol problem.

Here a stack trace:

Running tdd.br.com.ml.backend.services.log.SimpleArquillianTest 16:56:50,363 main INFO Log4j appears to be running in a Servlet environment, but there's no log4j-web module available. If you want better web container support, please add the log4j-web JAR to your web archive or server lib directory.2016-07-19 16:56:50,841 DEBUG [SimpleArquillianTest] Deployable test war: simple-test.war:/WEB-INF//WEB-INF/classes//WEB-INF/classes/br//WEB-INF/classes/br/com//WEB-INF/classes/br/com/ml//WEB-INF/classes/br/com/ml/backend//WEB-INF/classes/br/com/ml/backend/services//WEB-INF/classes/br/com/ml/backend/services/pedido//WEB-INF/classes/br/com/ml/backend/services/pedido/PedidoDTO.class/WEB-INF/classes/br/com/ml/backend/services/pedido/ItemDTO.class/WEB-INF/classes/log4j.xml/WEB-INF/beans.xmlXNIO version 3.3.4.FinalXNIO NIO Implementation Version 3.3.4.FinalJBoss Remoting version 4.0.18.FinalTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.855 sec <<< FAILURE! - in tdd.br.com.ml.backend.services.log.SimpleArquillianTestdeveria_injectar_pedido(tdd.br.com.ml.backend.services.log.SimpleArquillianTest) Time elapsed: 1.233 sec <<< ERROR!java.lang.IllegalStateException: Error launching test tdd.br.com.ml.backend.services.log.SimpleArquillianTest public void tdd.br.com.ml.backend.services.log.SimpleArquillianTest.deveria_injectar_pedido()Caused by: java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/simple-test/ArquillianServletRunner?outputMode=serializedObject&className=tdd.br.com.ml.backend.services.log.SimpleArquillianTest&methodName=deveria_injectar_pedido. No result returned

The test gets executed, as can be seen here:

2016-07-19 17:43:12,684 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/jboss/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/jboss/wildfly/standalone/configuration/logging.properties 2016-07-19 17:43:13,991 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 2016-07-19 17:43:14,012 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.3.4.Final 2016-07-19 17:43:14,023 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.4.Final 2016-07-19 17:43:14,083 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.18.Final 2016-07-19 17:43:14,123 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.hsqldb.jdbcDriver (version 2.3) 2016-07-19 17:43:14,130 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors 2016-07-19 17:43:14,135 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem. 2016-07-19 17:43:14,187 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final) 2016-07-19 17:43:14,194 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = hsqldb 2016-07-19 17:43:14,216 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main] 2016-07-19 17:43:14,243 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem 2016-07-19 17:43:14,324 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service 2016-07-19 17:43:14,332 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 2016-07-19 17:43:14,334 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 2016-07-19 17:43:14,355 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension 2016-07-19 17:43:14,363 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem 2016-07-19 17:43:14,380 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final 2016-07-19 17:43:14,413 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.15.Final starting 2016-07-19 17:43:14,413 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting 2016-07-19 17:43:14,552 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/opt/jboss/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 2016-07-19 17:43:14,583 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. 2016-07-19 17:43:14,584 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. 2016-07-19 17:43:14,584 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting 2016-07-19 17:43:14,583 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. 2016-07-19 17:43:14,691 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 2016-07-19 17:43:14,982 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments 2016-07-19 17:43:15,115 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final 2016-07-19 17:43:15,124 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4) 2016-07-19 17:43:15,223 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/jdbc/carf_test_integration] 2016-07-19 17:43:15,575 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management 2016-07-19 17:43:15,580 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990 2016-07-19 17:43:15,581 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 3552ms - Started 267 of 553 services (371 services are lazy, passive or on-demand) 2016-07-19 17:43:50,179 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/jboss/wildfly/standalone/data/content/39/9ad3f064785073f6c396fffb7cea4bc7314527/content 2016-07-19 17:43:50,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "simple-test.war" (runtime-name: "simple-test.war") 2016-07-19 17:43:50,690 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment simple-test.war 2016-07-19 17:43:50,738 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.2.3.Final 2016-07-19 17:43:50,949 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Starting Services for CDI deployment: simple-test.war 2016-07-19 17:43:50,976 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.2 (Final) 2016-07-19 17:43:51,018 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment simple-test.war 2016-07-19 17:43:51,888 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: /simple-test 2016-07-19 17:43:51,940 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "simple-test.war" (runtime-name : "simple-test.war") 2016-07-19 17:43:52,325 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Unregistered web context: /simple-test 2016-07-19 17:43:52,358 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment simple-test.war 2016-07-19 17:43:52,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment simple-test.war (runtime-name: simple-test.war) in 80ms 2016-07-19 17:43:52,418 INFO [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /opt/jboss/wildfly/standalone/data/content/39/9ad3f064785073f6c396fffb7cea4bc7314527/content 2016-07-19 17:43:52,418 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "simple-test.war" (runtime-name: "simple-test.war")

I am using the last version of Arquillian and the remote adapter:

        <dependency>
            <groupId>org.jboss.arquillian</groupId>
            <artifactId>arquillian-bom</artifactId>
            <version>1.1.11.Final</version>
            <scope>import</scope>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>org.wildfly.arquillian</groupId>
            <artifactId>wildfly-arquillian-container-remote</artifactId>
            <version>2.0.0.Final</version>
        </dependency>

This is my arquillian.xml

<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.org/schema/arquillian"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
    <engine>
        <property name="deploymentExportPath">target/deployments</property>
    </engine>
    <container qualifier="wildfly-remote" default="true">
        <configuration>
            <property name="managementAddress">192.168.0.84</property>
            <property name="managementPort">${wildfly.managementPort}</property>
            <property name="username">${wildfly.managementUser}</property>
            <property name="password">${wildfly.managementPassword}</property>
        </configuration>
    </container>
</arquillian>

And of course, the standard.xml (and believe me, I tried all kinds of combinations, with explicit IP and all):

    <?xml version='1.0' encoding='UTF-8'?>  
      
    <server xmlns="urn:jboss:domain:4.0">  
      
       ...  
      
      
       <interfaces>  
            <interface name="management">  
      
                 <inet-address value="${jboss.bind.address.management}"/>  
      
            </interface>  
            <interface name="public">  
                <any-address/>  
            </interface>  
        </interfaces>  
      
        <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">  
            <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>  
            <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>  
            <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>  
            <socket-binding name="http" port="${jboss.http.port:8080}"/>  
            <socket-binding name="https" port="${jboss.https.port:8443}"/>  
            <socket-binding name="txn-recovery-environment" port="4712"/>  
            <socket-binding name="txn-status-manager" port="4713"/>  
            <outbound-socket-binding name="mail-smtp">  
                <remote-destination host="localhost" port="25"/>  
            </outbound-socket-binding>  
        </socket-binding-group>  
      
    </server>

Hi,

I’m facing the same issue on JBoss EAP 7.0.4 with JBoss AS 10.1.2.Final. Any hints so far?

Best regards,
a-st

No, unfortunately. This is what keeps us from migrating to to latest version.

I’ve found out that issue is related to interface bindings in standalone.xml

This works fine:

<interfaces>  
    <interface name="management">  
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>  
    </interface>  
    <interface name="public">  
        <inet-address value="${jboss.bind.address:127.0.0.1}"/>  
    </interface>  
</interfaces>  

Anything else like

<interfaces>  
    <interface name="management">  
        <inet-address value="${jboss.bind.address.management:0.0.0.0}"/>  
    </interface>  
    <interface name="public">  
        <inet-address value="${jboss.bind.address:0.0.0.0}"/>  
    </interface>  
</interfaces>  

or

<interfaces>  
    <interface name="management">  
        <inet-address value="${jboss.bind.address.management:10.2.1.20}"/>  
    </interface>  
    <interface name="public">  
        <inet-address value="${jboss.bind.address:10.2.1.20}"/>  
    </interface>  
</interfaces>  

does not work (where 10.2.1.20 represents my LAN interface address).

Hi guys,
It seems that there is some issue with calculating IP address in the WF adapter.
Please check if this issue https://github.com/wildfly/wildfly-arquillian/pull/108 is similar as your one. You can also verify if the PR fixes you problem.

Hi, after applying mentioned pull request everything works as expected :wink:

Thank you very much!