0 Replies Latest reply on Oct 7, 2017 1:52 PM by Alexandre Vermeerbergen

    Arquilian Getting Started should mention a JRE 7 is required to run the test using standalone instance of JBoss AS

    Alexandre Vermeerbergen Newbie


      While forwarding the instructions from Getting Started · Arquillian Guides  as faithfully as possible, I felt in a trap when I was in this place of the article:


      To run the test on a standalone instance of JBoss AS, you first need to set it up. You can either:

      1. Download and unpack it in a location outside the project
      2. Use Maven to download and unpack it during a build

      Follow these steps to setup JBoss AS 7 outside the project:

      1. Download JBoss AS 7 (make sure the version you download matches the version of the jboss-as-arquillian-container-managed dependency in your pom.xml)
      2. Extract the archive
      3. (optional) Set the JBOSS_HOME environment variable to the path of the extracted directory

      If you have JBoss AS installed (i.e., extracted) and your JBOSS_HOME environment variable set to that location, you can activate the arquillian-jbossas-managed profile and run the test. You should see JBoss AS start in the console…and another "Green bar"!


      Instead of a green bar, the JUnit test not running, and Eclipse console was just displaying these messages:


      oct. 07, 2017 7:44:53 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal

      INFO: Starting container with: ["C:\Program Files\Java\jdk1.8.0_131\jre\bin\java", -Xmx512m, -XX:MaxPermSize=128m, -ea, -Djboss.home.dir=E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final, -Dorg.jboss.boot.log.file=E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final/standalone/log/boot.log, -Dlogging.configuration=file:E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final/standalone/configuration/logging.properties, -Djboss.modules.dir=E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\modules, -Djboss.bundles.dir=E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bundles, -jar, E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\jboss-modules.jar, -mp, E:\nosave\install\JBoss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone.xml]

      oct. 07, 2017 7:44:54 PM org.xnio.Xnio <clinit>

      INFO: XNIO Version 3.0.0.GA

      oct. 07, 2017 7:44:54 PM org.xnio.nio.NioXnio <clinit>

      INFO: XNIO NIO Implementation Version 3.0.0.GA

      oct. 07, 2017 7:44:54 PM org.jboss.remoting3.EndpointImpl <clinit>

      INFO: JBoss Remoting version 3.2.3.GA

      19:44:54,320 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      19:44:54,491 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      19:44:54,525 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting



      I used Eclise Oxygen, with ORACLE JDK 8 update 131 on Windows 7.


      I googled a little bit, until I found some references (not part of Arquillian · Write Real Tests  site) telling that this test isn't compatible with Java 8.

      So I added a "JRE 7" in my Eclipse preference, and I changed the JUnit's configuration to point to htis JRE 7, and then the test was successful.


      Would it be possible to add a warning in Getting Started · Arquillian Guides about this specific requirement for having a successful test with  JBoss AS ?


      By the way, JBoss AS seems to be no longer supporter, so maybe a better documentation fix would be to point to a supported application server, such a Wildfly or TomEE.


      Hope it helps,

      Alexandre Vermeerbergen