Esteve Aviles created ARQ-827: --------------------------------- Summary: mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final Key: ARQ-827 URL: https://issues.jboss.org/browse/ARQ-827 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: JBoss AS Containers Affects Versions: 1.0.0.CR7 Environment: Windows 7 and linux fedora 16 Reporter: Esteve Aviles Priority: Minor hi, This error appears when testing kitchensink application ( mvn test -Parq-jbossas-managed) I have just unzipped app server and quickstarts. No modification done. I am not using whitespaces.(C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink\) log4j:WARN No appenders could be found for logger (org.jboss.logging). log4j:WARN Please initialize the log4j system properly. 26-mar-2012 10:43:29 org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal INFO: Starting container with: ["C:\Archivos de programa\Java\jdk1.6.0_16\bin\java", -Xmx512m, -XX:MaxPermSize=128m, -Djboss.home.dir=C:\servers\jboss-as-7.1.0.Final, -Dorg.jboss.boot.log.file=C:\servers\jbo ss-as-7.1.0.Final/standalone/log/boot.log, -Dlogging.configuration=file:C:\servers\jboss-as-7.1.0.Final/standalone/configuration/logging.properties, -Djboss.modules.dir=C:\servers\jboss-as-7.1.0.Final\module s, -jar, C:\servers\jboss-as-7.1.0.Final\jboss-modules.jar, -mp, C:\servers\jboss-as-7.1.0.Final\modules, -logmodule, org.jboss.logmanager, -jaxpmodule, javax.xml.jaxp-provider, -mbeanserverbuildermodule, or g.jboss.as.jmx, org.jboss.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: -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: 5.303 sec <<< FAILURE! Results : Tests in error: org.jboss.as.quickstarts.kitchensink.test.MemberRegistrationTest: Could not start container Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 8.332s [INFO] Finished at: Mon Mar 26 10:43:32 CEST 2012 [INFO] Final Memory: 9M/16M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project jboss-as-kitchensink: There are test failures. [ERROR] [ERROR] Please refer to C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink\target\surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira