[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on AS7-4289:
------------------------------------
A, right. The problem is the quickstart/kitchensink pom is using 1.0.0.M1 of jboss-javaee-6.0-with-tools which expose 7.1.0.CRb1.. update the kitchensink pom to :
<javaee6.with.tools.version>1.0.0.M5</javaee6.with.tools.version>
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months
[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated AS7-4289:
-------------------------------
Assignee: Pete Muir
Component/s: (was: Test Suite)
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Assignee: Pete Muir
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months
[JBoss JIRA] (AS7-4220) CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-4220?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky resolved AS7-4220.
------------------------------------
Resolution: Done
Fixed.
> CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem
> ------------------------------------------------------------------------------------------
>
> Key: AS7-4220
> URL: https://issues.jboss.org/browse/AS7-4220
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.1.Final
> Reporter: Dave Ryan
> Assignee: Alexey Loubyansky
> Priority: Minor
> Fix For: 7.1.2.Final
>
>
> Potential typo in a description for the auto-deploy-exploded attribute of the deployment scanner. Says "zipped" where it should say "exploded". I suspect the cause is just copying and pasting the auto-deploy-zipped text but missing the "exploded" change.
> I've actually rewritten most of these descriptions in my documentation of the attributes for a reference topic. If you want to check those as potential updates, I can paste them in. I do imply assumed knowledge of boolean values to keep the sentences short.
> For example, I rewrote the auto-deployed-exploded as:
> "Allows the automatic deployment of exploded content without requiring a .dodeploy marker file. Recommended for only basic development scenarios to prevent exploded application deployment from occuring during changes by the developer or operating system."
> Was:
> "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content."
--
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
14 years, 2 months
[JBoss JIRA] (AS7-4291) CLONE - run.sh points at wrong file
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-4291:
-----------------------------------
Summary: CLONE - run.sh points at wrong file
Key: AS7-4291
URL: https://issues.jboss.org/browse/AS7-4291
Project: Application Server 7
Issue Type: Bug
Components: Scripts
Affects Versions: No Release
Environment: 86c9de3ad03f486f26adeb6335378f7ea36ec86d
Reporter: Radoslav Husar
Assignee: Brian Stansberry
{noformat}
[rhusar@rhusar jboss-as-7.1.2.Final-SNAPSHOT]$ ./bin/run.sh -c i_am_an_old_eap5_user.xml
========================================================================================
To start JBoss Application Server please see /home/rhusar/as/jboss-as-7.1.2.Final-SNAPSHOT/../README.txt
========================================================================================
[rhusar@rhusar jboss-as-7.1.2.Final-SNAPSHOT]$ cat /home/rhusar/as/jboss-as-7.1.2.Final-SNAPSHOT/../README.txt
cat: /home/rhusar/as/jboss-as-7.1.2.Final-SNAPSHOT/../README.txt: No such file or directory
[rhusar@rhusar jboss-as-7.1.2.Final-SNAPSHOT]$
{noformat}
--
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
14 years, 2 months
[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Esteve Aviles (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Esteve Aviles commented on AS7-4289:
------------------------------------
Same result against 7.1.1:
C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink>mvn test -Parq-jbossas-managed
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: kitchensink 7.1.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ jboss-as-kitchensink ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ jboss-as-kitchensink ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-kitchensink ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @ jboss-as-kitchensink ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ jboss-as-kitchensink ---
[INFO] Surefire report directory: C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.quickstarts.kitchensink.test.MemberRegistrationTest
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
26-mar-2012 13:33:40 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.1.Final, -Dorg.jboss.boot.log.file=C:\servers\jbo
ss-as-7.1.1.Final/standalone/log/boot.log, -Dlogging.configuration=file:C:\servers\jboss-as-7.1.1.Final/standalone/configuration/logging.properties, -Djboss.modules.dir=C:\servers\jboss-as-7.1.1.Final\module
s, -jar, C:\servers\jboss-as-7.1.1.Final\jboss-modules.jar, -mp, C:\servers\jboss-as-7.1.1.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: 2.736 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: 6.174s
[INFO] Finished at: Mon Mar 26 13:33:41 CEST 2012
[INFO] Final Memory: 8M/15M
[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
C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink>
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months
[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Esteve Aviles (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Esteve Aviles commented on AS7-4289:
------------------------------------
Indeed 7.1.0.Final
May I try 7.1.1?
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months
[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Tair Sabirgaliev (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Tair Sabirgaliev commented on AS7-4289:
---------------------------------------
{quote}
-Djboss.home.dir=C:\servers\jboss-as-7.1.0.Final
{quote}
Looks like it's indeed jboss-as-7.1.0
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months
[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on AS7-4289:
------------------------------------
Are you running the Quickstarts from 7.1.0.Final against a 7.1.1.Final server by any chance ?
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> 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
14 years, 2 months