Port conflict 8080 detection?
by Cheng Fang
I already have other servers running on port 8080, and then forgetfully
starting AS7 standalone server, and it started successfully without any
complaints. The main root page localhost:8080 stills displays the
content from the other server, but localhost:9990 does display as7
management console.
Is there a port conflict detection, or is it designed this way? I think
it would be helpful to fail fast once a port conflict is detected.
Cheng
13 years
Re: [jboss-as7-dev] Port conflict 8080 detection?
by Cheng Fang
Thanks Neven.
I just run standalone.sh to start as7, all the socket bindings are defaults.
JBoss Admin Command-line Interface
JBOSS_HOME: /Users/cfang/711
JBoss AS release: 7.1.1.Final "Brontes"
JAVA_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
java.version: 1.6.0_35
java.vm.vendor: Apple Inc.
java.vm.version: 20.10-b01-428
os.name: Mac OS X
os.version: 10.8.1
What's interesting is, it seems random which appserver has the port 8080
when both are running. My firefox displays as7 welcome page on
localhost:8080, while safari shows GlassFish welcome page.
I would expect some binding errors but I couldn't see any. I tried on
both 7.1.1 and 7.2 alpha1 with the same behavior.
Cheng
On 9/11/12 11:22 AM, Neven Cvetkovic wrote:
> Hey Chang,
>
> That's very strange. How are you starting your JBoss AS7? What does it
> say for http connector? What port is it bound to? What IP does it bind to?
>
> Anyhow, you should see something like this in the log files/console -
> if the port is already bound by some other process (on that IP, e.g.
> 127.0.0.1):
>
> 11:15:31,595 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC
> service thread 1-10) Error initializing
> endpoint:java.net.BindException: Address already in use
> /127.0.0.1:8080 <http://127.0.0.1:8080>
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:983)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190)
> [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983)
> [jbossweb-7.0.13.Final.jar:]
> at
> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA <http://1.0.2.GA>]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA <http://1.0.2.GA>]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [classes.jar:1.6.0_33]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [classes.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
>
> 11:15:31,820 ERROR [org.jboss.msc.service.fail] (MSC service thread
> 1-10) MSC00001: Failed to start service jboss.web.connector.http:
> org.jboss.msc.service.StartException in service
> jboss.web.connector.http: JBAS018007: Error starting web connector
> at
> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA <http://1.0.2.GA>]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA <http://1.0.2.GA>]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [classes.jar:1.6.0_33]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [classes.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
> Caused by: LifecycleException: Protocol handler initialization
> failed: java.net.BindException: Address already in use /127.0.0.1:8080
> <http://127.0.0.1:8080>
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at
> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> ....
> 11:15:33,950 INFO [org.jboss.as.controller] (Controller Boot Thread)
> JBAS014774: Service status report
> JBAS014777: Services which failed to start: service
> jboss.web.connector.http: org.jboss.msc.service.StartException in
> service jboss.web.connector.http: JBAS018007: Error starting web connector
> ...
> 11:15:35,487 INFO [org.jboss.as <http://org.jboss.as>] (MSC service
> thread 1-10) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 11:15:35,487 ERROR [org.jboss.as <http://org.jboss.as>] (MSC service
> thread 1-10) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with
> errors) in 31877ms - Started 173 of 251 services (1 services failed or
> missing dependencies, 76 services are passive or on-demand)
> ...
>
>
> If you don't have any errors, you should see something like this:
> ...
> 11:18:55,607 INFO [org.apache.coyote.http11.Http11Protocol] (MSC
> service thread 1-13) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
> ...
> 11:18:56,356 INFO [org.jboss.as <http://org.jboss.as>] (Controller
> Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 11:18:56,357 INFO [org.jboss.as <http://org.jboss.as>] (Controller
> Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in
> 4052ms - Started 133 of 208 services (74 services are passive or
> on-demand)
> ...
>
>
>
> Hope that helps.
>
> Cheers!
> Neven
>
>
>
> On Tue, Sep 11, 2012 at 11:12 AM, Cheng Fang <cfang(a)redhat.com
> <mailto:cfang@redhat.com>> wrote:
>
> I don't see any either on console or server.log. The other
> servers are
> Tomcat or GlassFish, both run on 8080 by default.
>
> Cheng
>
> On 9/11/12 10:49 AM, Brian Stansberry wrote:
> > There were no complaints in the logs?
> >
> > On 9/11/12 9:37 AM, Cheng Fang wrote:
> >> I already have other servers running on port 8080, and then
> forgetfully
> >> starting AS7 standalone server, and it started successfully
> without any
> >> complaints. The main root page localhost:8080 stills displays the
> >> content from the other server, but localhost:9990 does display as7
> >> management console.
> >>
> >> Is there a port conflict detection, or is it designed this way?
> I think
> >> it would be helpful to fail fast once a port conflict is detected.
> >>
> >> Cheng
> >> _______________________________________________
> >> jboss-as7-dev mailing list
> >> jboss-as7-dev(a)lists.jboss.org
> <mailto:jboss-as7-dev@lists.jboss.org>
> >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >>
> >
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
13 years
warning on startup jbos 7.1.1 and jersey
by ofer lilian
18:13:23,458 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException'
for service type 'org.apache.cxf.bus.factory'
18:13:23,463 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,467 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,472 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,478 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,482 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,486 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,490 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,493 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,497 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,501 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,504 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,509 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,515 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,518 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,522 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,526 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,530 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,534 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,538 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,542 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,546 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,550 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,554 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,558 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,562 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,566 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,569 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,573 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,577 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,581 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,585 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,590 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,594 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,598 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,602 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,606 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,610 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,614 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,617 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,621 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,625 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,629 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,632 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,633 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,636 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,637 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,637 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,638 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,639 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,640 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,641 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider'
for service type 'com.sun.jersey.spi.StringReaderProvider'
18:13:23,642 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,643 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,643 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,648 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,648 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,649 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,650 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,651 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,651 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,652 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,653 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,653 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,654 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,655 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,656 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyReader'
18:13:23,656 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,657 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,658 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,658 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,659 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,660 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,660 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,661 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,662 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General'
for service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,663 WARN [org.jboss.as.server.deployment] JBAS015893: Encountered
invalid class name
'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for
service type 'javax.ws.rs.ext.MessageBodyWriter'
18:13:23,794 WARN [org.jboss.as.dependency.private] JBAS018567: Deployment
"deployment.VrmServer.ear" is using a private module
("org.apache.cxf:main") which may be changed or removed in future versions
without notice.
18:13:23,795 WARN [org.jboss.as.dependency.private] JBAS018567: Deployment
"deployment.VrmServer.ear" is using a private module
("org.apache.cxf:main") which may be changed or removed in future versions
without notice.
13 years
[Proposal] Create minimal distribution as generic service container
by Olaf Bergner
While I think that JBoss AS 7's architecture and implementation are
outstanding neither I nor the company I'm working for have a need for a
JEE container. What we *do* have a need for, though, is a robust,
performant, flexibel and manageable runtime for deploying our networked
services in. Having taken a look at JBoss AS 7's Modular Service
Container, its extension mechanism, its flexibel configuration model and
the fact that it's based on JBoss Modules I started to think that a
JBoss AS 7 distribution stripped down to its core just might fit the bill.
Beyond creating that minimal distribution itself I think all it would
take is to add some documentation, especially on how to use the Modular
Service Container, something I couldn't find *any* documentation for.
Plus maybe a sample application or two. Provided someone in the know
volunteered to assist me I would be more than willing to provide those.
What do you think?
Regards,
Olaf
13 years
Build failed in Jenkins: as7-7.1-testsuite #582
by ci-builds＠redhat.com
See <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
------------------------------------------
[...truncated 21028 lines...]
[WARNING] The directory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...,> which is a base directory of a ValidationSet or TransformationSet, does not exist.
[WARNING] No files found for transformation by stylesheet <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.trace-logging) @ jboss-as-testsuite-benchmark ---
[WARNING] The directory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...,> which is a base directory of a ValidationSet or TransformationSet, does not exist.
[WARNING] No files found for transformation by stylesheet <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-testsuite-benchmark ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-testsuite-benchmark ---
[INFO] No tests to run.
[INFO] Surefire report directory: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss Application Server Test Suite: Stress Tests 7.1.3.Final-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jboss-as-testsuite-stress ---
[INFO] Deleting <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (ban-bad-dependencies) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.0:create-timestamp (get-build-timestamp) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.0:create (get-scm-revision) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- maven-help-plugin:2.1.1:active-profiles (help.active-profiles) @ jboss-as-testsuite-stress ---
[INFO] Active profile report written to: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-help-plugin:2.1.1:effective-pom (help.effective-pom) @ jboss-as-testsuite-stress ---
[INFO] Effective-POM written to: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-help-plugin:2.1.1:effective-settings (help.effective-settings) @ jboss-as-testsuite-stress ---
[INFO] Effective-settings written to: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-help-plugin:2.1.1:system (help.system) @ jboss-as-testsuite-stress ---
[INFO] System report written to: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- properties-maven-plugin:1.0-alpha-2:write-project-properties (default) @ jboss-as-testsuite-stress ---
[INFO]
[INFO] --- maven-dependency-plugin:2.3:copy (copy-annotations-endorsed) @ jboss-as-testsuite-stress ---
[INFO] Configured Artifact: org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:?:jar
[INFO] Copying jboss-annotations-api_1.1_spec-1.0.1.Final.jar to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ jboss-as-testsuite-stress ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-resources-plugin:2.5:copy-resources (ts.copy-jbossas.groups) @ jboss-as-testsuite-stress ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-testsuite-stress ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.ip) @ jboss-as-testsuite-stress ---
[WARNING] The directory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...,> which is a base directory of a ValidationSet or TransformationSet, does not exist.
[WARNING] No files found for transformation by stylesheet <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- xml-maven-plugin:1.0:transform (ts.config-as.trace-logging) @ jboss-as-testsuite-stress ---
[WARNING] The directory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...,> which is a base directory of a ValidationSet or TransformationSet, does not exist.
[WARNING] No files found for transformation by stylesheet <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-testsuite-stress ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-testsuite-stress ---
[INFO] No tests to run.
[INFO] Surefire report directory: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [5.637s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [2.791s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.327s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.174s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [16.633s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [7.388s]
[INFO] JBoss Application Server: Controller Core ......... SUCCESS [31.645s]
[INFO] JBoss Application Server: Domain Management ....... SUCCESS [8.477s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [4.423s]
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [3.366s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [4.721s]
[INFO] JBoss Application Server: Platform MBean integration SUCCESS [7.465s]
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [10.492s]
[INFO] JBoss Application Server: Network ................. SUCCESS [3.902s]
[INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [12.244s]
[INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [6.239s]
[INFO] JBoss Application Server: Server .................. SUCCESS [17.602s]
[INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [10.688s]
[INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [16.202s]
[INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [13.976s]
[INFO] JBoss Application Server: EE ...................... SUCCESS [12.074s]
[INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [16.184s]
[INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [10.285s]
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.473s]
[INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.472s]
[INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [5.322s]
[INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [11.535s]
[INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [43.151s]
[INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [12.187s]
[INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [17.480s]
[INFO] JBoss Application Server: Clustered registry service SUCCESS [3.043s]
[INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [28.968s]
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [5.865s]
[INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [5.276s]
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [7.590s]
[INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [30.123s]
[INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.215s]
[INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [13.944s]
[INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [5.805s]
[INFO] JBoss Application Server: Config Assembly ......... SUCCESS [3.092s]
[INFO] JBoss Application Server: Command line interface .. SUCCESS [12.062s]
[INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.333s]
[INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.452s]
[INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [4.047s]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [4.465s]
[INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [3.205s]
[INFO] JBoss Application Server: Clustered singleton services SUCCESS [4.991s]
[INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [24.423s]
[INFO] JBoss Application Server: Config Admin ............ SUCCESS [6.670s]
[INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [9.293s]
[INFO] JBoss Application Server: EE Deployment ........... SUCCESS [6.570s]
[INFO] JBoss Application Server: JAXR Client ............. SUCCESS [6.274s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.219s]
[INFO] JBoss Application Server: JPA SPI ................. SUCCESS [9.067s]
[INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [2.128s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [7.835s]
[INFO] JBoss Application Server: Weld Integration ........ SUCCESS [12.090s]
[INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [8.315s]
[INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.240s]
[INFO] JBoss Application Server: JDR ..................... SUCCESS [6.510s]
[INFO] JBoss Application Server: JSF Support jar ......... SUCCESS [8.388s]
[INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [6.932s]
[INFO] JBoss Application Server: Management Client Content SUCCESS [2.945s]
[INFO] JBoss Application Server: Host Controller ......... SUCCESS [16.738s]
[INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [13.399s]
[INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [9.317s]
[INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [16.312s]
[INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [9.569s]
[INFO] JBoss Application Server: OSGi .................... SUCCESS [0.206s]
[INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [10.798s]
[INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [5.513s]
[INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [8.067s]
[INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [1.720s]
[INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [6.091s]
[INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [6.554s]
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [3.488s]
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [3.868s]
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [8.828s]
[INFO] JBoss Application Server: Build ................... SUCCESS [1:01.014s]
[INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.193s]
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [2.542s]
[INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.261s]
[INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.250s]
[INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [24.211s]
[INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.430s]
[INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.198s]
[INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [22.453s]
[INFO] JBoss Application Server: Arquillian Common Domain SUCCESS [3.573s]
[INFO] JBoss Application Server: Arquillian Remote Domain Container SUCCESS [2.208s]
[INFO] JBoss Application Server: Arquillian Managed Domain Container SUCCESS [38.901s]
[INFO] JBoss Application Server: Distribution ............ SUCCESS [9.543s]
[INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [5.302s]
[INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [1.744s]
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [2.923s]
[INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [13.777s]
[INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [18.630s]
[INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [6.663s]
[INFO] JBoss Application Server Test Suite: Integration - Smoke SUCCESS [2:21.443s]
[INFO] JBoss Application Server Test Suite: Integration - Basic FAILURE [12:18.765s]
[INFO] JBoss Application Server Test Suite: Integration - Clustering SUCCESS [13:04.791s]
[INFO] JBoss Application Server Test Suite: Integration - IIOP SUCCESS [41.187s]
[INFO] JBoss Application Server Test Suite: Integration - XTS FAILURE [47.237s]
[INFO] JBoss Application Server Test Suite: Integration - Multinode Tests SUCCESS [57.939s]
[INFO] JBoss Application Server Test Suite: Integration - Manual Mode Tests FAILURE [2:44.871s]
[INFO] JBoss Application Server Test Suite: Compatibility Tests FAILURE [1:05.356s]
[INFO] JBoss Application Server Test Suite: Domain Mode Integration Tests FAILURE [6:36.614s]
[INFO] JBoss Application Server Test Suite: Benchmark Tests SUCCESS [1:01.752s]
[INFO] JBoss Application Server Test Suite: Stress Tests . SUCCESS [3.016s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 57:17.150s
[INFO] Finished at: Thu Sep 06 17:13:37 EDT 2012
[INFO] Final Memory: 252M/465M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (basic-integration-default-web.surefire) on project jboss-as-ts-integ-basic: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> for the individual test results.
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (tests-xts.surefire) on project jboss-as-ts-integ-xts: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> for the individual test results.
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (manualmode.surefire) on project jboss-as-ts-integ-manualmode: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> for the individual test results.
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-testsuite-compat: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> for the individual test results.
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-testsuite-integration-domain: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> 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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jboss-as-ts-integ-basic
+ gzip testsuite/integration/basic/target/jbossas/standalone/log/server.log
+ exit 1
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
13 years, 1 month
