[JBoss JIRA] (AS7-4209) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-4209:
-------------------------------------
Summary: Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode
Key: AS7-4209
URL: https://issues.jboss.org/browse/AS7-4209
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.1.Final
Environment: Server running in Domain mode
Reporter: Wolf-Dieter Fink
Assignee: Brian Stansberry
It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode.
All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration.
The domain server will receive the informations if a host-controller enrol and register server to a clustered server-group.
So the configuration of the initial_hosts can be done automaticaly to avoid old entries which cause unnecessary checks and ensure that all active servers are known.
--
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-4059) Allow RestartParentXXXHandlers to handle resources with multiple services
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-4059:
----------------------------------------
Summary: Allow RestartParentXXXHandlers to handle resources with multiple services
Key: AS7-4059
URL: https://issues.jboss.org/browse/AS7-4059
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Richard Achmatowicz
Assignee: Jason Greene
Priority: Minor
I'd like to use RestartParentWriteAttributeHandler to allow handling of attributes which, when updated, case a restart of only the services installed by their parent resource. These are really useful classes and solve a commonly encountered problem.
However, the resource I want to restart involves four services, and it appears that RestartParentWriteAttriubuteHandler assumes that for every parent key name, there is only a single service registered.
If we had the private methods:
ServiceName[] getParentServiceNames(PathAddress address)
boolean areParentServicesInstalled(ServiceName[] names)
void removeServices(OperationContext context, ServiceNames[] names, ModelNode parentModel)
this could be made to work for more general resources.
--
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] Created: (AS7-1735) Console: failure when creating new JMS should provide more information
by Radoslav Husar (JIRA)
Console: failure when creating new JMS should provide more information
----------------------------------------------------------------------
Key: AS7-1735
URL: https://issues.jboss.org/browse/AS7-1735
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.0.1.Final
Reporter: Radoslav Husar
Assignee: Heiko Braun
Say I try to create a queue, but input incorrect values, the console provides the following which is not enough to know what was the root cause:
{code}
Tue Sep 06 12:52:33 GMT+200 2011
Failed to create queue
Unexpected HTTP response: 500
Request
{
"operation" => "add",
"address" => [
("profile" => "default"),
("subsystem" => "messaging"),
("jms-queue" => "asdas")
],
"entries" => ["dasdasd"],
"durable" => false,
"selector" => "*"
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => {"server-groups" => [("main-server-group" => {"master" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => {"Failed services" => {"jboss.messaging.jms.queue.asdas" => "org.jboss.msc.service.StartException in service jboss.messaging.jms.queue.asdas: failed to create queue"}},
"rolled-back" => true
}
}})]},
"failure-description" => "Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
{code}
while the server says:
{code}
[Server:server-one] 12:52:33,840 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.messaging.jms.queue.asdas: org.jboss.msc.service.StartException in service jboss.messaging.jms.queue.asdas: failed to create queue
[Server:server-one] at org.jboss.as.messaging.jms.JMSQueueService.start(JMSQueueService.java:60)
[Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
[Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
[Server:server-one] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
[Server:server-one] Caused by: HornetQException[errorCode=103 message=Invalid filter: * Encountered "*" at line 1, column 1.
[Server:server-one] Was expecting one of:
[Server:server-one] "TRUE" ...
[Server:server-one] "FALSE" ...
[Server:server-one] "NOT" ...
[Server:server-one] "(" ...
[Server:server-one] "-" ...
[Server:server-one] "+" ...
[Server:server-one] <INTEGER_LITERAL> ...
[Server:server-one] <FLOATING_POINT_LITERAL> ...
[Server:server-one] <SIMPLE_STRING> ...
[Server:server-one] <IDENTIFIER> ...
[Server:server-one] ]
[Server:server-one] at org.hornetq.core.filter.impl.FilterImpl.<init>(FilterImpl.java:117)
[Server:server-one] at org.hornetq.core.filter.impl.FilterImpl.createFilter(FilterImpl.java:97)
[Server:server-one] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1694)
[Server:server-one] at org.hornetq.core.server.impl.HornetQServerImpl.deployQueue(HornetQServerImpl.java:1060)
[Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateQueue(JMSServerManagerImpl.java:1046)
[Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.access$100(JMSServerManagerImpl.java:98)
[Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl$1.runException(JMSServerManagerImpl.java:422)
[Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1643)
[Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.createQueue(JMSServerManagerImpl.java:413)
[Server:server-one] at org.jboss.as.messaging.jms.JMSQueueService.start(JMSQueueService.java:58)
[Server:server-one] ... 5 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBWEB-235) "max-active-sessions" functionality to limit the number of sessions works as designed, but does not result in a (configured) error page to be shown to the end-user
by Tom Fonteyne (JIRA)
Tom Fonteyne created JBWEB-235:
----------------------------------
Summary: "max-active-sessions" functionality to limit the number of sessions works as designed, but does not result in a (configured) error page to be shown to the end-user
Key: JBWEB-235
URL: https://issues.jboss.org/browse/JBWEB-235
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tomcat
Affects Versions: JBossWeb-2.1.12.GA
Environment: all
Reporter: Tom Fonteyne
Assignee: Remy Maucherat
Attachments: sessionlimit.war, source.tar.gz
Configuring a webapp via jboss-web.xml to limit (and passivate) the number of active sessions work fine, and an exception gets thrown/logged in the server.log:
16:45:03,454 FATAL [JspFactoryImpl] Exception initializing page context
java.lang.IllegalStateException: createSession(): number of active sessions exceeds the maximum limit: 2 when trying to create session
at org.jboss.web.tomcat.service.session.JBossCacheManager.createSessionInternal(JBossCacheManager.java:497)
at org.jboss.web.tomcat.service.session.JBossCacheManager.createSession(JBossCacheManager.java:448)
at org.apache.catalina.connector.Request.doGetSession(Request.java:2373)
at org.apache.catalina.connector.Request.getSession(Request.java:2100)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:844)
at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:146)
at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:124)
at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryImpl.java:107)
at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java:63)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:44)
...
so far so good. But, we would expect "java.lang.IllegalStateException" to cause the error mechanisme to kick in due to in web.xml:
<error-page>
<exception-type>java.lang.IllegalStateException</exception-type>
<location>/max.html</location>
</error-page>
This does not happen, and the end-user is presented with an empty screen in his browser likely thinking that the site went down.
Note that when the 3th user hits a servlet at his first request, the error-page is shown correctly - so this issue is limited to Jasper.
--
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, 3 months
[JBoss JIRA] (AS7-4289) Quickstart / Kitchensink example v X refer to older JBoss AS 7 version Y via jboss-javaee-6.0-with-tools
by Esteve Aviles (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Esteve Aviles commented on AS7-4289:
------------------------------------
Ok,
Tried updating pom <javaee6.with.tools.version>1.0.0.M5</javaee6.with.tools.version> and works well.
Thank you very much.
Regrads,
> Quickstart / Kitchensink example v X refer to older JBoss AS 7 version Y via jboss-javaee-6.0-with-tools
> --------------------------------------------------------------------------------------------------------
>
> 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
>
> QuickStart 7.1.0.Final refer to JBoss AS 7.1.0.CRb1 via jboss-javaee-6.0-with-tools 1.0.0.M1
> jboss-javaee-6.0-with-tools M5 refer to JBoss AS 7.1.0.Final
> 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, 3 months
[JBoss JIRA] (AS7-4294) Invocation of RecoveryStoreProxy from the client side via JMX fails
by Ivo Studensky (JIRA)
Ivo Studensky created AS7-4294:
----------------------------------
Summary: Invocation of RecoveryStoreProxy from the client side via JMX fails
Key: AS7-4294
URL: https://issues.jboss.org/browse/AS7-4294
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.1.Final
Reporter: Ivo Studensky
Assignee: Jason Greene
Fix For: 7.1.2.Final
The RecoveryStoreProxy does not currently work on AS7 when it is called from the client side because of broken serialization of Uid class. It fails with the following exception:
{noformat}
Caused by: java.io.NotActiveException: Fields were never written
at org.jboss.marshalling.river.RiverObjectOutputStream.finish(RiverObjectOutputStream.java:175)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1009)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
at org.jboss.remotingjmx.protocol.v1.ClientConnection$TheConnection$15.write(ClientConnection.java:1181)
at org.jboss.remotingjmx.protocol.v1.Common.write(Common.java:179)
at org.jboss.remotingjmx.protocol.v1.ClientConnection$TheConnection.invoke(ClientConnection.java:1163)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
... 92 more
Caused by: an exception which occurred:
in object com.arjuna.ats.arjuna.common.Uid@0
{noformat}
More details can be found in project jira - JBTM-1076.
--
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, 3 months
[JBoss JIRA] (AS7-4289) Quickstart / Kitchensink example v X refer to older JBoss AS 7 version Y via jboss-javaee-6.0-with-tools
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated AS7-4289:
-------------------------------
Summary: Quickstart / Kitchensink example v X refer to older JBoss AS 7 version Y via jboss-javaee-6.0-with-tools (was: mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final)
Description:
QuickStart 7.1.0.Final refer to JBoss AS 7.1.0.CRb1 via jboss-javaee-6.0-with-tools 1.0.0.M1
jboss-javaee-6.0-with-tools M5 refer to JBoss AS 7.1.0.Final
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
was:
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
> Quickstart / Kitchensink example v X refer to older JBoss AS 7 version Y via jboss-javaee-6.0-with-tools
> --------------------------------------------------------------------------------------------------------
>
> 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
>
> QuickStart 7.1.0.Final refer to JBoss AS 7.1.0.CRb1 via jboss-javaee-6.0-with-tools 1.0.0.M1
> jboss-javaee-6.0-with-tools M5 refer to JBoss AS 7.1.0.Final
> 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, 3 months