1 2 Previous Next 28 Replies Latest reply: Aug 13, 2012 6:25 PM by Ivo Neskovic RSS

arquillian and jboss 7.1

Riccardo Pasquini Novice

Hi people,

 

i was trying to skill myself with arquillian and tried to create a test... no problem so far... the problem is when i try to run the test using AS7.1, this is the outcome:

 

 

-------------------------------------------------------

T E S T S

-------------------------------------------------------

Concurrency config is parallel='methods', perCoreThreadCount=true, threadCount=10, useUnlimitedThreads=false

log4j:WARN No appenders could be found for logger (org.jboss.logging).

log4j:WARN Please initialize the log4j system properly.

3-feb-2012 13.43.29 org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal

INFO: Starting container with: ["C:\Program Files (x86)\Java\jdk1.6.0_27\bin\java", -Xmx512m, -XX:MaxPermSize=128m, -Djboss.home.dir=C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT/standalone/log/boot.log, -Dlogging.configuration=file:C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.modules.dir=C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\modules, -jar, C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\jboss-modules.jar, -mp, C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\modules, -logmodule, org.jboss.logmanager, -jaxpmodule, javax.xml.jaxp-provider, -mbeanserverbuildermodule, org.jboss.as.jmx, org.jboss.as.standalone, -server-config, standalone.xml]

Invalid option '-logmodule'

Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]

       java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]

       java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]

       java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]

where <module-spec> is a valid module specification string

and options include:

    -help         Display this message

    -modulepath <search path of directories>

 

 

i've checked the sources of that class and the logmodule option is hardcoded. Is it a compatibility issue or i'm doing something wrong?

 

Thanks

  • 1. Re: arquillian and jboss 7.1
    jaikiran pai Master

    Try it against the latest AS7 nightly build, that should be fixed (you'll just see a WARN about the logmodule option, instead of an exception).

  • 2. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    Partial success but the issue is still a blocker one for my test case:

     

     

    -------------------------------------------------------

    T E S T S

    -------------------------------------------------------

    Concurrency config is parallel='methods', perCoreThreadCount=true, threadCount=10, useUnlimitedThreads=false

    log4j:WARN No appenders could be found for logger (org.jboss.logging).

    log4j:WARN Please initialize the log4j system properly.

    4-feb-2012 19.53.58 org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal

    INFO: Starting container with: ["C:\Program Files (x86)\Java\jdk1.6.0_27\bin\java", -Xmx512m, -XX:MaxPermSize=128m, -Djboss.home.dir=C:\Program Files (x86)\J\jboss-as-7.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT/standalone/log/boot.log, -Dlogging.configtion=file:C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.modules.dir=C:\Program Files (x86)\J\jboss-as-7.1.0.Final-SNAPSHOT\modules, -jar, C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\jboss-modules.jar, -mp, C:\Program Files (x86)\Java\js-as-7.1.0.Final-SNAPSHOT\modules, -logmodule, org.jboss.logmanager, -jaxpmodule, javax.xml.jaxp-provider, -mbeanserverbuildermodule, org.jboss.as.jmx, org.js.as.standalone, -server-config, standalone.xml]

    WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.

    Invalid option '-mbeanserverbuildermodule'

    Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]

    where <module-spec> is a valid module specification string

    and options include:

        [omissis]

        -jaxpmodule <module-name>

                      The default JAXP implementation to use of the JDK

        -version      Print version and exit

    Exception in thread "Thread-1" java.lang.ArrayIndexOutOfBoundsException: 6

            at org.apache.maven.surefire.util.internal.ByteBuffer.append(ByteBuffer.java:45)

            at org.apache.maven.surefire.booter.ForkingRunListener.info(ForkingRunListener.java:223)

            at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.writeTestOutput(ConcurrentReporterManager.java:175)

            at org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:88)

            at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer$ConsoleConsumer.run(ManagedDeployableContainer.java:250)

            at java.lang.Thread.run(Thread.java:662)

    Running com.hp.dragon.business.translation.TranslatorPropertyFileBackEndBeanTest

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec <<< FAILURE!

     

     

    Results :

     

     

    Tests in error:

      com.hp.dragon.business.translation.TranslatorPropertyFileBackEndBeanTest: Could not start container

     

     

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0

     

     

    [INFO] ------------------------------------------------------------------------

    [INFO] BUILD FAILURE

    [INFO] ------------------------------------------------------------------------

     

     

    Thank you for your time

    bye

  • 3. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    Calling the standalone.batç

     

     

    Calling "C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\bin\standalone.conf.bat"

    ===============================================================================

     

     

      JBoss Bootstrap Environment

     

     

      JBOSS_HOME: C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

     

      JAVA: c:\Program Files (x86)\Java\jdk1.6.0_27\bin\java

     

     

      JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se

    rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman

     

     

    ===============================================================================

     

     

    Exception in thread "main" java.lang.ExceptionInInitializerError

            at org.jboss.as.server.Main.main(Main.java:73)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

            at java.lang.reflect.Method.invoke(Method.java:597)

            at org.jboss.modules.Module.run(Module.java:260)

            at org.jboss.modules.Main.main(Main.java:291)

    Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jbos

    s.logmanager.LogManager")

            at org.jboss.logmanager.Logger.getLogger(Logger.java:60)

            at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)

            ... 7 more

     

  • 4. Re: arquillian and jboss 7.1
    Stephen Coy Master

    Does the example attached to Testing secured EJBs on JBoss AS7.1.x with Arquillian work for you?

  • 5. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    As expected, i get the same error:

    WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.

    Invalid option '-mbeanserverbuildermodule'

    Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]

           java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]

    where <module-spec> is a valid module specification string

    and options include:

        -help         Display this message

        -modulepath <search path of directories>

        -mp <search path of directories>

                      A list of directories, separated by ';', where modules may be located

                      If not specified, the value of the "module.path" system property is used

        -class        Specify that the final argument is a

                      class to load from the class path; not compatible with -jar

        -cp,-classpath <search path of archives or directories>

                      A search path for class files; implies -class

        -dep,-dependencies <module-spec>[,<module-spec>,...]

                      A list of module dependencies to add to the class path;

                      requires -class or -cp

        -jar          Specify that the final argument is the name of a

                      JAR file to run as a module; not compatible with -class

        -config <config-location>

                      The location of the module configuration.  Either -mp or -config

                      may be specified, but not both

        -jaxpmodule <module-name>

                      The default JAXP implementation to use of the JDK

        -version      Print version and exit

     

     

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.229 sec <<< FAILURE!

    Running org.jboss.arquillian.secureejb.demo.CallerPrincipalDemoSessionBeanIT

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec <<< FAILURE!

    Running org.jboss.arquillian.secureejb.demo.IsCallerInRoleDemoSessionBeanIT

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec <<< FAILURE!

     

     

    Results :

     

     

    Tests in error:

      org.jboss.arquillian.secureejb.demo.AuthorisationAnnotationDemoBeanIT: Could not start container

      org.jboss.arquillian.secureejb.demo.CallerPrincipalDemoSessionBeanIT: Arquillian has previously been attempted initialized, but failed. See cause for previous

    exception

      org.jboss.arquillian.secureejb.demo.IsCallerInRoleDemoSessionBeanIT: Arquillian has previously been attempted initialized, but failed. See cause for previous

    exception

     

     

    Tests run: 3, Failures: 0, Errors: 3, Skipped: 0

     

     

    Pay attention, i'm using current nightly build which it seems to be completely broken (it fails to start regardless arquillian)

     

    bye

  • 6. Re: arquillian and jboss 7.1
    jaikiran pai Master

    Riccardo Pasquini wrote:

     

    Pay attention, i'm using current nightly build which it seems to be completely broken

    It's not We have various tests and Jenkins job which run almost every hour and they are working fine. Infact if there's a single genuine test failure, the commit isn't pushed upstream.

     

    What exactly are you trying to run? AS7 build or a project of your own? How have you configured Arquillian?

     

     

    org.jboss.arquillian.secureejb.demo.AuthorisationAnnotationDemoBeanIT: Could not start container

    The exact errors will be present in the test's output file somewhere in the target/surefire-reports folder. What do those logs say?

  • 7. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    mmm my environment is very easy: win7 with JBOSS_HOME set to C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

    opening explorer and clicking on standalone.bat gets the following outcome:

     

    Calling "C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT\bin\standalone.conf.bat"

    ===============================================================================

     

     

      JBoss Bootstrap Environment

     

     

      JBOSS_HOME: C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

     

      JAVA: c:\Program Files (x86)\Java\jdk1.6.0_27\bin\java

     

     

      JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se

    rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman

     

     

    ===============================================================================

     

     

    Exception in thread "main" java.lang.ExceptionInInitializerError

            at org.jboss.as.server.Main.main(Main.java:73)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

            at java.lang.reflect.Method.invoke(Method.java:597)

            at org.jboss.modules.Module.run(Module.java:260)

            at org.jboss.modules.Main.main(Main.java:291)

    Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jbos

    s.logmanager.LogManager")

            at org.jboss.logmanager.Logger.getLogger(Logger.java:60)

            at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)

            ... 7 more

    Press any key to continue . . .

     

    how can you say that the nightly build is ok?

  • 8. Re: arquillian and jboss 7.1
    jaikiran pai Master

    Riccardo Pasquini wrote:

     

    mmm my environment is very easy: win7 with JBOSS_HOME set to C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

    That's the problem. Don't install Java or JBoss in a folder containing spaces in its path name. Move them to something like C:\Java\jboss-as-7.1.0.Final-SNAPSHOT.

     

     

    Riccardo Pasquini wrote:

     

    how can you say that the nightly build is ok?

    Based on various (internal and external) Jenkins jobs including this one http://hudson.jboss.org/hudson/job/JBoss-AS-7.x-latest/. And like I said, the build runs numerous tests (in thousands) for each commit/push. And if a single test fails, that commit won't make it upstream.

  • 9. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    jaikiran pai ha scritto:

     

    What exactly are you trying to run? AS7 build or a project of your own? How have you configured Arquillian?

    in that case, i have not configured nothing... just used suggested test case

    org.jboss.arquillian.secureejb.demo.AuthorisationAnnotationDemoBeanIT: Could not start container

    The exact errors will be present in the test's output file somewhere in the target/surefire-reports folder. What do those logs say?

    -------------------------------------------------------------------------------

    Test set: org.jboss.arquillian.secureejb.demo.AuthorisationAnnotationDemoBeanIT

    -------------------------------------------------------------------------------

    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.229 sec <<< FAILURE!

    org.jboss.arquillian.secureejb.demo.AuthorisationAnnotationDemoBeanIT  Time elapsed: 0 sec  <<< ERROR!

    org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container

              at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:170)

              at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:78)

              at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

              at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

              at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

              at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

              at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

              at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)

              at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

              at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

              at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

              at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)

              at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

              at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)

              at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)

              at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)

              at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)

              at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)

              at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68)

              at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)

              at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)

              at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)

              at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)

              at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)

              at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)

              at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)

              at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

    Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s

              at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:166)

              ... 68 more

  • 10. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    jaikiran pai ha scritto:

     

    Riccardo Pasquini wrote:

     

    mmm my environment is very easy: win7 with JBOSS_HOME set to C:\Program Files (x86)\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

    That's the problem. Don't install Java or JBoss in a folder containing spaces in its path name. Move them to something like C:\Java\jboss-as-7.1.0.Final-SNAPSHOT.

     

    changing jboss_home to C:\Java\etcetcetc and retry

     

    thnx

  • 11. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    Arquillian integration still fails:

     

    C:\Users\pasquinr\Tmp\arquillian-security-demo>echo %JBOSS_HOME%

    C:\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

    same reported error

     

    standalone launch

     

    c:\Java\jboss-as-7.1.0.Final-SNAPSHOT\bin>echo %JBOSS_HOME%

    C:\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

     

    c:\Java\jboss-as-7.1.0.Final-SNAPSHOT\bin>standalone.bat

     

    works properly

  • 12. Re: arquillian and jboss 7.1
    Stephen Coy Master

    Riccardo Pasquini wrote:

     

    ...

              at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

    Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [30] s

              at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:166)

              ... 68 more

     

    This makes me wonder if its not a Windows firewall problem, or some other networking issue.

  • 13. Re: arquillian and jboss 7.1
    jaikiran pai Master

    Riccardo Pasquini wrote:

     

    Arquillian integration still fails:

     

    C:\Users\pasquinr\Tmp\arquillian-security-demo>echo %JBOSS_HOME%

    C:\Java\jboss-as-7.1.0.Final-SNAPSHOT

     

    same reported error

     

    Check the standalone/log/server.log and boot.log to see what it's failing at.

  • 14. Re: arquillian and jboss 7.1
    Riccardo Pasquini Novice

    @Stephen, i must sadly say that windows is not my choice :___(

    anyway, after the spaceless path fix, the AS starts if not managed in arquillian

     

    @Jaikiran, i've removed the log directory to have a clean scenario... that folder is created at start... that's what happens when running AS as standalone... that folder is not created when running the arquillian test

     

    running my test adds this information:

     

    Exception in thread "Thread-1" java.lang.ArrayIndexOutOfBoundsException: 6

            at org.apache.maven.surefire.util.internal.ByteBuffer.append(ByteBuffer.java:45)

            at org.apache.maven.surefire.booter.ForkingRunListener.info(ForkingRunListener.java:223)

            at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.writeTestOutput(ConcurrentReporterManager.java:175)

            at org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:88)

            at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer$ConsoleConsumer.run(ManagedDeployableContainer.java:250)

            at java.lang.Thread.run(Thread.java:662)

     

    maybe it can help

1 2 Previous Next