[JBoss JIRA] (WFLY-115) JMSService error during :reload operation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-115?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-115:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 951649|https://bugzilla.redhat.com/show_bug.cgi?id=951649] from MODIFIED to ON_QA
> JMSService error during :reload operation
> -----------------------------------------
>
> Key: WFLY-115
> URL: https://issues.jboss.org/browse/WFLY-115
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.Alpha1
>
>
> if the admin client performs a :reload operation, the JMSService throws an exception and HornetQ server is not stopped properly and do not release its resources:
> {noformat}
> 20:01:54,480 ERROR [org.jboss.messaging] (MSC service thread 1-1) JBAS011602: Exception while stopping JMS server: java.lang.IllegalStateException: Service already removed
> at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:792) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:775) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl.setMode(ServiceControllerImpl.java:754) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.as.messaging.jms.JMSService$1.deActivate(JMSService.java:103) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.hornetq.core.server.impl.HornetQServerImpl.callDeActiveCallbacks(HornetQServerImpl.java:1374) [hornetq-server-2.3.0.CR2.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:598) [hornetq-server-2.3.0.CR2.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:542) [hornetq-server-2.3.0.CR2.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:509) [hornetq-server-2.3.0.CR2.jar:]
> at org.hornetq.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:502) [hornetq-jms-server-2.3.0.CR2.jar:]
> at org.jboss.as.messaging.jms.JMSService.stop(JMSService.java:119) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> {noformat}
> When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (WFLY-62) AS 8: Testsuite fails on Solaris SPARC 10
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-62?page=com.atlassian.jira.plugin.sy... ]
RH Bugzilla Integration commented on WFLY-62:
---------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 921574|https://bugzilla.redhat.com/show_bug.cgi?id=921574] from MODIFIED to ON_QA
> AS 8: Testsuite fails on Solaris SPARC 10
> -----------------------------------------
>
> Key: WFLY-62
> URL: https://issues.jboss.org/browse/WFLY-62
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41
> Reporter: Frank Langelage
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha1
>
> Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml
>
>
> Compiling the current sources from github fails for me on this environment.
> On Windows everything is fine.
> Compiling 7.2.0.Final works in this environment.
> But regarding this test, nothing seems to have changed in between.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec
> Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
> Running org.jboss.as.naming.InitialContextTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE!
> Running org.jboss.as.naming.InitialContextFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
> Running org.jboss.as.naming.NamingEventCoordinatorTestCase
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
> Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec
> Running org.jboss.as.naming.InMemoryNamingStoreTestCase
> Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
> Running org.jboss.as.naming.ObjectFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
> Running org.jboss.as.naming.NamingContextTestCase
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
> Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
> Results :
> Tests in error:
> testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null
> Tests run: 70, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s]
> [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s]
> [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s]
> [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s]
> [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s]
> [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSF ..................... SKIPPED
> [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED
> [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: System JMX Module ....... SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Build Modular ........... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED
> [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:36.380s
> [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013
> [INFO] Final Memory: 122M/348M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures.
> [ERROR]
> [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-naming
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1303?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside commented on WFLY-1303:
---------------------------------------
Ah, I'm using Camel and Jetty is used by various components to run embedded web services as Camel endpoints.. I cannot remove jetty.
As for the others, I'll take a look and trim it down.. But jetty I cannot remove..
> metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-1303
> URL: https://issues.jboss.org/browse/WFLY-1303
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Tomaz Cerar
>
> metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
> web.xml:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
> version="3.0"
> metadata-complete="true">
> <listener>
> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
> </listener>
> <context-param>
> <param-name>contextConfigLocation</param-name>
> <param-value>WEB-INF/spring/root-context.xml</param-value>
> </context-param>
> </web-app>
> {code}
> Server.log output when deploying a war that contains the lib jersey-container-servlet-2.0-rc1.jar.
> {code}
> awhiteside@localhost jboss-as-8.0.0.Alpha1-SNAPSHOT# ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT
> JAVA: /usr/local/java/bin/java
> JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 19:20:03,372 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final
> 19:20:03,516 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.2.Final
> 19:20:03,567 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> 19:20:04,293 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.1.0.CR2
> 19:20:04,296 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 19:20:04,297 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.1.0.CR2
> 19:20:04,311 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.16.GA
> 19:20:04,354 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 19:20:04,357 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.16.Final)
> 19:20:04,385 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012605: Activated the following JSF Implementations: [main]
> 19:20:04,389 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
> 19:20:04,398 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
> 19:20:04,405 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 19:20:04,413 INFO [org.jboss.as.undertow] (MSC service thread 1-8) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 19:20:04,414 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2
> 19:20:04,428 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
> 19:20:04,430 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.16.Final
> 19:20:04,436 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 19:20:04,439 INFO [org.jboss.as.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 19:20:04,440 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 19:20:04,581 INFO [io.undertow] (ServerService Thread Pool -- 47) Creating file handler for path /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/welcome-content
> 19:20:04,611 INFO [org.jboss.as.undertow] (MSC service thread 1-1) Starting server server service: service jboss.undertow.server.default-server
> 19:20:04,619 INFO [org.jboss.as.undertow] (MSC service thread 1-3) Starting host default-host
> 19:20:04,619 INFO [org.jboss.as.undertow] (MSC service thread 1-3) registering handler io.undertow.server.handlers.resource.ResourceHandler@4155a5c7 under path '/'
> 19:20:04,624 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Alpha1
> 19:20:04,692 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
> 19:20:04,815 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
> 19:20:04,815 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
> 19:20:04,825 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/standalone/deployments
> 19:20:04,831 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
> 19:20:04,850 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 19:20:05,466 INFO [io.undertow.servlet] (MSC service thread 1-1) jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
> 19:20:05,520 INFO [org.jboss.as.undertow] (MSC service thread 1-1) JBAS018210: Register web context: /hawtio
> 19:20:05,547 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "hawtio.war" (runtime-name : "hawtio.war")
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 19:20:05,627 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 2545ms - Started 198 of 234 services (55 services are lazy, passive or on-demand)
> 19:20:15,567 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "messaging-gateway.war" (runtime-name: "messaging-gateway.war")
> 19:20:17,769 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jaxb-api.jar in /content/messaging-gateway.war/WEB-INF/lib/jaxb-impl-2.2.6.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,770 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-api.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-extra.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_l10n.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,771 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_ja.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_zh.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_fr.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_de.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_es.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_it.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_sw.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_ko.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt_zh_TW.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-rt-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,777 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry webservices-rt.jar in /content/messaging-gateway.war/WEB-INF/lib/webservices-tools-2.2.1-1.jar does not point to a valid jar for a Class-Path reference.
> 19:20:17,806 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.kxml2.io.KXmlParser,org.kxml2.io.KXmlSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
> 19:20:17,810 INFO [org.jboss.as.pojo] (MSC service thread 1-3) JBAS017000: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 19:20:17,936 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,942 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component org.eclipse.jetty.server.handler.StatisticsHandler$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.eclipse.jetty.server.handler.StatisticsHandler$1
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,944 WARN [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1
> at org.jboss.as.ee.component.DefaultInterceptorConfigurator.configure(DefaultInterceptorConfigurator.java:93) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) [jboss-as-ee-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 19:20:17,972 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.undertow.deployment.default-host./messaging-gateway: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./messaging-gateway: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:176)
> at org.jboss.as.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:129)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> ... 3 more
> Caused by: java.lang.NullPointerException
> at io.undertow.servlet.spec.ServletRegistrationImpl.getClassName(ServletRegistrationImpl.java:152)
> at org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer.addServletWithExistingRegistration(JerseyServletContainerInitializer.java:222)
> at org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer.onStartup(JerseyServletContainerInitializer.java:136)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:153)
> ... 6 more
> 19:20:17,987 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./messaging-gateway" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./messaging-gateway: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 19:20:18,035 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment messaging-gateway.war (runtime-name: messaging-gateway.war) in 48ms
> 19:20:18,037 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."messaging-gateway.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."messaging-gateway.war".deploymentCompleteService]
> service jboss.deployment.unit."messaging-gateway.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."messaging-gateway.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-host./messaging-gateway
> {code}
> jboss-deployment-structure.xml
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <exclude-subsystems>
> <subsystem name="jaxrs"/>
> <subsystem name="webservices"/>
> </exclude-subsystems>
> <exclusions>
> <module name="org.slf4j"/>
> <module name="org.slf4j.impl"/>
> <module name="org.slf4j.ext"/>
> <module name="org.slf4j.jcl-over-slf4j"/>
> <module name="org.apache.commons.logging"/>
> <module name="org.apache.log4j"/>
> <!--<module name="org.hibernate"/>-->
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> {code}
> The class in question it is trying to instantiate..
> {code}
> package org.glassfish.jersey.servlet.init;
> ...
> @HandlesTypes({Path.class, Provider.class, Application.class, ApplicationPath.class})
> public class JerseyServletContainerInitializer implements ServletContainerInitializer {
> .....
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (WFLY-1304) No way to remove/exclude/disable resteasy for a given WAR
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-1304?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-1304:
--------------------------------------
This is because the jar is imported as part of the javaee.api module, which is basically just an agregate module of the javaee API's. If you exclude this as well it should work.
Implicit dependencies on this module will hopefully be removed at some point before the Wildfly final release.
> No way to remove/exclude/disable resteasy for a given WAR
> ---------------------------------------------------------
>
> Key: WFLY-1304
> URL: https://issues.jboss.org/browse/WFLY-1304
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Services
> Environment: JBoss AS 7.2.0.Final, couldn't select that version anywhere in Jira?
> Reporter: Aaron Whiteside
> Assignee: Stuart Douglas
>
> I am including Jersey 2.0 jars in my WAR:
> {code}
> WEB-INF/lib/javax.ws.rs-api-2.0-rc3.jar
> WEB-INF/lib/jersey-common-2.0-rc1.jar
> WEB-INF/lib/jersey-media-json-jettison-2.0-rc1.jar
> WEB-INF/lib/jersey-container-servlet-core-2.0-rc1.jar
> WEB-INF/lib/jersey-client-2.0-rc1.jar
> WEB-INF/lib/jersey-container-servlet-2.0-rc1.jar
> WEB-INF/lib/jersey-server-2.0-rc1.jar
> WEB-INF/lib/jersey-proxy-client-2.0-rc1.jar
> {code}
> jboss-deployment-structure.xml
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <exclude-subsystems>
> <subsystem name="resteasy"/>
> <subsystem name="jaxrs"/>
> <subsystem name="webservices"/>
> </exclude-subsystems>
> <exclusions>
> <module name="org.slf4j"/>
> <module name="org.slf4j.impl"/>
> <module name="org.slf4j.ext"/>
> <module name="org.slf4j.jcl-over-slf4j"/>
> <module name="org.apache.commons.logging"/>
> <module name="org.apache.log4j"/>
> <module name="javax.ws.rs.api"/>
> <module name="org.jboss.resteasy" />
> <module name="org.jboss.resteasy.resteasy-atom-provider" />
> <module name="org.jboss.resteasy.resteasy-cdi" />
> <module name="org.jboss.resteasy.resteasy-jaxrs" />
> <module name="org.jboss.resteasy.resteasy-jaxb-provider" />
> <module name="org.jboss.resteasy.resteasy-jackson-provider" />
> <module name="org.jboss.resteasy.resteasy-jsapi" />
> <module name="org.jboss.resteasy.resteasy-multipart-provider" />
> <module name="org.jboss.resteasy.async-http-servlet-30" />
> <!--<module name="org.hibernate"/>-->
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> {code}
> Yet I am getting NoSuchMethodError because JBoss won't stop exporting it's own JAX-RS packages over the jars embedded in my war despite my attempts to disable it via jboss-deployment-structure.xml.
> {code}
> javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:321) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:372) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:335) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:218) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:681) ~[jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:449) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1084) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:376) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1018) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.Server.handle(Server.java:451) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:252) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:266) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:240) [jetty-io-9.0.2.v20130417.jar:9.0.2.v20130417]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [na:1.7.0_13]
> Caused by: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
> at org.glassfish.jersey.servlet.internal.ResponseWriter.rethrow(ResponseWriter.java:219) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.internal.ResponseWriter.failure(ResponseWriter.java:201) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:343) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:223) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:231) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:275) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:257) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:191) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:819) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:311) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> ... 17 common frames omitted
> Caused by: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
> at org.glassfish.jersey.message.internal.OutboundJaxrsResponse.from(OutboundJaxrsResponse.java:97) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ContainerResponse.<init>(ContainerResponse.java:88) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:341) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:101) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:217) ~[jersey-server-2.0-rc1.jar:na]
> ... 26 common frames omitted
> 20:01:05.816 WARN [Camel (camelContext) thread #10 - wsgw://0.0.0.0:3456] org.eclipse.jetty.servlet.ServletHandler -
> javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:321) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:372) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:335) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:218) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:681) ~[jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:449) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1084) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:376) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1018) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.Server.handle(Server.java:451) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:252) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:266) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:240) [jetty-io-9.0.2.v20130417.jar:9.0.2.v20130417]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [na:1.7.0_13]
> Caused by: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at org.glassfish.jersey.servlet.internal.ResponseWriter.rethrow(ResponseWriter.java:219) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.internal.ResponseWriter.failure(ResponseWriter.java:201) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:343) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:223) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:231) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:275) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:257) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[jersey-common-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:191) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:819) ~[jersey-server-2.0-rc1.jar:na]
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:311) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
> ... 17 common frames omitted
> Caused by: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:64) ~[javax.ws.rs-api-2.0-rc3.jar:na]
> at javax.ws.rs.NotFoundException.<init>(NotFoundException.java:60) ~[javax.ws.rs-api-2.0-rc3.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:213) ~[jersey-server-2.0-rc1.jar:na]
> ... 26 common frames omitted
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (WFLY-1304) No way to remove/exclude/disable resteasy for a given WAR
by Aaron Whiteside (JIRA)
Aaron Whiteside created WFLY-1304:
-------------------------------------
Summary: No way to remove/exclude/disable resteasy for a given WAR
Key: WFLY-1304
URL: https://issues.jboss.org/browse/WFLY-1304
Project: WildFly
Issue Type: Bug
Components: Web (Undertow), Web Services
Affects Versions: 8.0.0.Alpha1
Environment: JBoss AS 7.2.0.Final, couldn't select that version anywhere in Jira?
Reporter: Aaron Whiteside
Assignee: Stuart Douglas
I am including Jersey 2.0 jars in my WAR:
{code}
WEB-INF/lib/javax.ws.rs-api-2.0-rc3.jar
WEB-INF/lib/jersey-common-2.0-rc1.jar
WEB-INF/lib/jersey-media-json-jettison-2.0-rc1.jar
WEB-INF/lib/jersey-container-servlet-core-2.0-rc1.jar
WEB-INF/lib/jersey-client-2.0-rc1.jar
WEB-INF/lib/jersey-container-servlet-2.0-rc1.jar
WEB-INF/lib/jersey-server-2.0-rc1.jar
WEB-INF/lib/jersey-proxy-client-2.0-rc1.jar
{code}
jboss-deployment-structure.xml
{code}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<exclude-subsystems>
<subsystem name="resteasy"/>
<subsystem name="jaxrs"/>
<subsystem name="webservices"/>
</exclude-subsystems>
<exclusions>
<module name="org.slf4j"/>
<module name="org.slf4j.impl"/>
<module name="org.slf4j.ext"/>
<module name="org.slf4j.jcl-over-slf4j"/>
<module name="org.apache.commons.logging"/>
<module name="org.apache.log4j"/>
<module name="javax.ws.rs.api"/>
<module name="org.jboss.resteasy" />
<module name="org.jboss.resteasy.resteasy-atom-provider" />
<module name="org.jboss.resteasy.resteasy-cdi" />
<module name="org.jboss.resteasy.resteasy-jaxrs" />
<module name="org.jboss.resteasy.resteasy-jaxb-provider" />
<module name="org.jboss.resteasy.resteasy-jackson-provider" />
<module name="org.jboss.resteasy.resteasy-jsapi" />
<module name="org.jboss.resteasy.resteasy-multipart-provider" />
<module name="org.jboss.resteasy.async-http-servlet-30" />
<!--<module name="org.hibernate"/>-->
</exclusions>
</deployment>
</jboss-deployment-structure>
{code}
Yet I am getting NoSuchMethodError because JBoss won't stop exporting it's own JAX-RS packages over the jars embedded in my war despite my attempts to disable it via jboss-deployment-structure.xml.
{code}
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:321) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:372) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:335) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:218) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:681) ~[jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:449) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1084) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:376) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1018) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.Server.handle(Server.java:451) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:252) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:266) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:240) [jetty-io-9.0.2.v20130417.jar:9.0.2.v20130417]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [na:1.7.0_13]
Caused by: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
at org.glassfish.jersey.servlet.internal.ResponseWriter.rethrow(ResponseWriter.java:219) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.internal.ResponseWriter.failure(ResponseWriter.java:201) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:343) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:223) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:231) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:275) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:257) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:191) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:819) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:311) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
... 17 common frames omitted
Caused by: java.lang.NoSuchMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
at org.glassfish.jersey.message.internal.OutboundJaxrsResponse.from(OutboundJaxrsResponse.java:97) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ContainerResponse.<init>(ContainerResponse.java:88) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:341) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:101) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:217) ~[jersey-server-2.0-rc1.jar:na]
... 26 common frames omitted
20:01:05.816 WARN [Camel (camelContext) thread #10 - wsgw://0.0.0.0:3456] org.eclipse.jetty.servlet.ServletHandler -
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:321) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:372) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:335) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:218) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:681) ~[jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:449) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1084) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:376) [jetty-servlet-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1018) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.Server.handle(Server.java:451) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:252) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:266) [jetty-server-9.0.2.v20130417.jar:9.0.2.v20130417]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:240) [jetty-io-9.0.2.v20130417.jar:9.0.2.v20130417]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [na:1.7.0_13]
Caused by: org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
at org.glassfish.jersey.servlet.internal.ResponseWriter.rethrow(ResponseWriter.java:219) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.internal.ResponseWriter.failure(ResponseWriter.java:201) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:343) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:223) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:231) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:275) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:257) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:227) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[jersey-common-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:191) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:819) ~[jersey-server-2.0-rc1.jar:na]
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:311) ~[jersey-container-servlet-core-2.0-rc1.jar:na]
... 17 common frames omitted
Caused by: java.lang.NoSuchMethodError: javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
at javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:64) ~[javax.ws.rs-api-2.0-rc3.jar:na]
at javax.ws.rs.NotFoundException.<init>(NotFoundException.java:60) ~[javax.ws.rs-api-2.0-rc3.jar:na]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:213) ~[jersey-server-2.0-rc1.jar:na]
... 26 common frames omitted
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months