[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 edited comment on WFLY-1303 at 5/1/13 11:28 AM:
----------------------------------------------------------------
Excluding the javax* and other various jars has no effect, it just seems that JBoss ignores the metadata-complete attribute in web.xml.
was (Author: Aaron.Whiteside):
Excluding the javax* and other various jars has not effect, it just seems that JBoss ignores the metadata-complete attribute in web.xml.
> 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
11 years
- 1
- 0
[JBoss JIRA] (WFLY-1304) No way to remove/exclude/disable resteasy for a given WAR
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1304?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside commented on WFLY-1304:
---------------------------------------
No luck with excluding javaee.api...
{code}
11:22:20,279 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "messaging-gateway.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
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.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) [rt.jar:1.7.0_13]
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3098) [rt.jar:1.7.0_13]
at java.lang.Class.getAnnotation(Class.java:3057) [rt.jar:1.7.0_13]
at java.lang.Class.isAnnotationPresent(Class.java:3070) [rt.jar:1.7.0_13]
at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:134)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
... 5 more
11:22:20,283 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"messaging-gateway.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"messaging-gateway.war\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"}}
{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="javaee.api"/>
<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"/>
</exclusions>
<dependencies>
<module name="javax.activation.api"/>
<module name="javax.annotation.api"/>
<module name="javax.ejb.api"/>
<module name="javax.el.api"/>
<module name="javax.enterprise.api"/>
<module name="javax.inject.api"/>
<module name="javax.interceptor.api"/>
<module name="javax.jms.api"/>
<!--<module name="javax.jws.api"/>-->
<module name="javax.mail.api"/>
<module name="javax.management.j2ee.api"/>
<module name="javax.persistence.api"/>
<module name="javax.resource.api"/>
<module name="javax.rmi.api"/>
<module name="javax.security.auth.message.api"/>
<module name="javax.security.jacc.api"/>
<module name="javax.servlet.api"/>
<module name="javax.servlet.jsp.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<!--<module name="javax.ws.rs.api"/>-->
<module name="javax.xml.bind.api" />
<!--<module name="javax.xml.soap.api" />-->
<!--<module name="javax.xml.ws.api" />-->
<module name="javax.api" />
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
> 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
11 years
- 1
- 0
[JBoss JIRA] (WFLY-1304) No way to remove/exclude/disable resteasy for a given WAR
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1304?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside edited comment on WFLY-1304 at 5/1/13 11:24 AM:
----------------------------------------------------------------
No luck with excluding javaee.api... Now I get this error..
{code}
11:22:20,279 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "messaging-gateway.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
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.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) [rt.jar:1.7.0_13]
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3098) [rt.jar:1.7.0_13]
at java.lang.Class.getAnnotation(Class.java:3057) [rt.jar:1.7.0_13]
at java.lang.Class.isAnnotationPresent(Class.java:3070) [rt.jar:1.7.0_13]
at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:134)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
... 5 more
11:22:20,283 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"messaging-gateway.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"messaging-gateway.war\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"}}
{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="javaee.api"/>
<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"/>
</exclusions>
<dependencies>
<module name="javax.activation.api"/>
<module name="javax.annotation.api"/>
<module name="javax.ejb.api"/>
<module name="javax.el.api"/>
<module name="javax.enterprise.api"/>
<module name="javax.inject.api"/>
<module name="javax.interceptor.api"/>
<module name="javax.jms.api"/>
<!--<module name="javax.jws.api"/>-->
<module name="javax.mail.api"/>
<module name="javax.management.j2ee.api"/>
<module name="javax.persistence.api"/>
<module name="javax.resource.api"/>
<module name="javax.rmi.api"/>
<module name="javax.security.auth.message.api"/>
<module name="javax.security.jacc.api"/>
<module name="javax.servlet.api"/>
<module name="javax.servlet.jsp.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<!--<module name="javax.ws.rs.api"/>-->
<module name="javax.xml.bind.api" />
<!--<module name="javax.xml.soap.api" />-->
<!--<module name="javax.xml.ws.api" />-->
<module name="javax.api" />
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
was (Author: Aaron.Whiteside):
No luck with excluding javaee.api...
{code}
11:22:20,279 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "messaging-gateway.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
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.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) [rt.jar:1.7.0_13]
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) [rt.jar:1.7.0_13]
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3098) [rt.jar:1.7.0_13]
at java.lang.Class.getAnnotation(Class.java:3057) [rt.jar:1.7.0_13]
at java.lang.Class.isAnnotationPresent(Class.java:3070) [rt.jar:1.7.0_13]
at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:134)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
... 5 more
11:22:20,283 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "messaging-gateway.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"messaging-gateway.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"messaging-gateway.war\"
Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"}}
{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="javaee.api"/>
<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"/>
</exclusions>
<dependencies>
<module name="javax.activation.api"/>
<module name="javax.annotation.api"/>
<module name="javax.ejb.api"/>
<module name="javax.el.api"/>
<module name="javax.enterprise.api"/>
<module name="javax.inject.api"/>
<module name="javax.interceptor.api"/>
<module name="javax.jms.api"/>
<!--<module name="javax.jws.api"/>-->
<module name="javax.mail.api"/>
<module name="javax.management.j2ee.api"/>
<module name="javax.persistence.api"/>
<module name="javax.resource.api"/>
<module name="javax.rmi.api"/>
<module name="javax.security.auth.message.api"/>
<module name="javax.security.jacc.api"/>
<module name="javax.servlet.api"/>
<module name="javax.servlet.jsp.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<!--<module name="javax.ws.rs.api"/>-->
<module name="javax.xml.bind.api" />
<!--<module name="javax.xml.soap.api" />-->
<!--<module name="javax.xml.ws.api" />-->
<module name="javax.api" />
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
> 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
11 years
- 1
- 0
[JBoss JIRA] (JBAS-9536) Add property expansion capability to .wsdl files
by david.boeren (JIRA)
david.boeren created JBAS-9536:
----------------------------------
Summary: Add property expansion capability to .wsdl files
Key: JBAS-9536
URL: https://issues.jboss.org/browse/JBAS-9536
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 6.1.0
Reporter: david.boeren
Assignee: Alessio Soldano
Priority: Minor
The customer is doing JMS-based webservices using the following declarations in their wsdl file (referred to using the wsdllocation annotation):
<soapjms:jndiConnectionFactoryName>myqueue</soapjms:jndiConnectionFactoryName> <soapjms:jndiInitialContextFactory>com.vendor.InitialContextFactory</soapjms:jndiInitialContextFactory>
<soapjms:jndiURL>$MY_URL</soapjms:jndiURL>
The $MY_URL is the url of the messaging server. Since property replacement does not work for wsdl files they need to manually modify this before deploying and package separate versions of their app for each environment. If property expansion worked in the .wsdl this would no longer be necessary.
--
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
11 years
- 1
- 0
[JBoss JIRA] (WFLY-818) Slave host does not register to DC when starting with --cached-dc and DC is available
by Jaromir Hamala (JIRA)
[ https://issues.jboss.org/browse/WFLY-818?page=com.atlassian.jira.plugin.s... ]
Jaromir Hamala commented on WFLY-818:
-------------------------------------
I'm afraid that this issue effectively makes DC to be a Single Point of Failure. You have these options:
1. starting the HC with --cached-dc, but it effectively downgrades it to a standalone mode as is never attempts to contact DC
2. do not use the --cached-dc, but than you HC will fail to start if DC is not available
Given there is no guide how to make DC highly available, it's a very unfortunate situation and possible a showstopper for deploying JBoss.
> Slave host does not register to DC when starting with --cached-dc and DC is available
> -------------------------------------------------------------------------------------
>
> Key: WFLY-818
> URL: https://issues.jboss.org/browse/WFLY-818
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Manel Martinez Gonzalez
>
> NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... )
> When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc
--
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
11 years
- 1
- 0
[JBoss JIRA] (JBRULES-3666) kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3666?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration updated JBRULES-3666:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=868913, https://bugzilla.redhat.com/show_bug.cgi?id=958394 (was: https://bugzilla.redhat.com/show_bug.cgi?id=868913)
> kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBRULES-3666
> URL: https://issues.jboss.org/browse/JBRULES-3666
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.5.0.Beta1
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 5.5.0.Final
>
>
> When you add the same KnowledgeBaseEventListener to kbase twice, kbase holds both KnowledgeBaseEventListenerWrapper instances. I'm not 100% sure if this is a bug but I guess KnowledgeBaseEventListenerWrapper should implement equals() method like StatefulKnowledgeSessionImpl$AgendaEventListenerWrapper.
--
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
11 years
- 1
- 0
[JBoss JIRA] (JBRULES-3666) kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3666?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on JBRULES-3666:
--------------------------------------------------
Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 958394|https://bugzilla.redhat.com/show_bug.cgi?id=958394]
+++ This bug was initially created as a clone of Bug #868913 +++
Description of problem:
Platform BZ for JBRULES-3666
Steps to Reproduce:
Actual results:
Expected results:
I think the unit test which is sent as the pull request would be fine.
https://github.com/droolsjbpm/drools/pull/153
--- Additional comment from JBoss JIRA Server on 2012-11-01 08:16:54 EDT ---
Mario Fusco <mario.fusco(a)gmail.com> updated the status of jira JBRULES-3666 to Resolved
> kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBRULES-3666
> URL: https://issues.jboss.org/browse/JBRULES-3666
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.5.0.Beta1
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 5.5.0.Final
>
>
> When you add the same KnowledgeBaseEventListener to kbase twice, kbase holds both KnowledgeBaseEventListenerWrapper instances. I'm not 100% sure if this is a bug but I guess KnowledgeBaseEventListenerWrapper should implement equals() method like StatefulKnowledgeSessionImpl$AgendaEventListenerWrapper.
--
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
11 years
- 1
- 0
[JBoss JIRA] (JBRULES-3699) Large memory allocation per request in drools-camel-server
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3699?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration updated JBRULES-3699:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=882155, https://bugzilla.redhat.com/show_bug.cgi?id=958387 (was: https://bugzilla.redhat.com/show_bug.cgi?id=882155)
> Large memory allocation per request in drools-camel-server
> ----------------------------------------------------------
>
> Key: JBRULES-3699
> URL: https://issues.jboss.org/browse/JBRULES-3699
> Project: JBRULES
> Issue Type: Quality Risk
> Security Level: Public(Everyone can see)
> Components: drools-camel
> Affects Versions: 5.4.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mark Proctor
> Attachments: JBoss_Benchmark_Request.xml, numbers.drl
>
>
> In drools-camel-server, memory allocation during request/response message handling is quite larger than actual request/response size.
> For example, with attached numbers.drl and JBoss_Benchmark_Request.xml, one SOAP request results in 45MB+ object allocation while the actual request size is 200KB and the response size is 650KB. They are short-lived objects so wouldn't be a memory leak but affect performance especially under high load.
--
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
11 years
- 1
- 0
[JBoss JIRA] (JBRULES-3723) 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3723?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration updated JBRULES-3723:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=904038, https://bugzilla.redhat.com/show_bug.cgi?id=958385 (was: https://bugzilla.redhat.com/show_bug.cgi?id=904038)
> 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails
> -----------------------------------------
>
> Key: JBRULES-3723
> URL: https://issues.jboss.org/browse/JBRULES-3723
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-compiler-DSL
> Affects Versions: 5.5.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mark Proctor
>
> When DSL contains ' ' (='IDEOGRAPHIC SPACE' (U+3000)), DSLMapLexer fails with "DSL lexer error" (Internally, it's a NoViableAltException). IDEOGRAPHIC SPACE is commonly used in Japan so please allow it to use. It doesn't mean that I want to use IDEOGRAPHIC SPACE as an alternative to ASCII whitespace. Just to use it as same as usual unicode characters.
--
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
11 years
- 1
- 0
[JBoss JIRA] (JBRULES-3723) 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3723?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on JBRULES-3723:
--------------------------------------------------
Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 958385|https://bugzilla.redhat.com/show_bug.cgi?id=958385]
+++ This bug was initially created as a clone of Bug #904038 +++
Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBRULES-3723
Steps to Reproduce:
1. include ' ' (='IDEOGRAPHIC SPACE' (U+3000)) in DSL.
See the following pull request for test case.
https://github.com/droolsjbpm/drools/pull/173
Actual results:
kbuilder.add() fails with "DSL lexer error"
Expected results:
Being able to use ' ' as usual unicode characters
> 'IDEOGRAPHIC SPACE' (U+3000) in DSL fails
> -----------------------------------------
>
> Key: JBRULES-3723
> URL: https://issues.jboss.org/browse/JBRULES-3723
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-compiler-DSL
> Affects Versions: 5.5.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mark Proctor
>
> When DSL contains ' ' (='IDEOGRAPHIC SPACE' (U+3000)), DSLMapLexer fails with "DSL lexer error" (Internally, it's a NoViableAltException). IDEOGRAPHIC SPACE is commonly used in Japan so please allow it to use. It doesn't mean that I want to use IDEOGRAPHIC SPACE as an alternative to ASCII whitespace. Just to use it as same as usual unicode characters.
--
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
11 years
- 1
- 0