[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1303?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1303:
------------------------------
Component/s: Web (Undertow)
(was: Web (JBoss Web))
> 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: Remy Maucherat
>
> 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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Aaron Whiteside (JIRA)
Aaron Whiteside created WFLY-1303:
-------------------------------------
Summary: 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 (JBoss Web)
Affects Versions: 8.0.0.Alpha1
Reporter: Aaron Whiteside
Assignee: Remy Maucherat
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-962) Unable to combine Resource Archive (RAR) <dependencies> and <exclusions> directives in jboss-deployment-structure.xml without <exclusions> being ignored
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-962?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on WFLY-962:
-------------------------------------
According to the EE specification RAR dependencies have to expose all transitive dependencies of the RAR as well. Because the RAR also has a dependency on log4j this dependency will be imported from the RAR.
If you also exclude log4j from the RAR this should work.
> Unable to combine Resource Archive (RAR) <dependencies> and <exclusions> directives in jboss-deployment-structure.xml without <exclusions> being ignored
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-962
> URL: https://issues.jboss.org/browse/WFLY-962
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Environment: Linux (CentOS 6.3), JDK 1.6.0_37
> Reporter: Matthew White
> Assignee: Stuart Douglas
> Attachments: jbossas-bugexample.zip
>
>
> I have an EAR file where for a WAR sub-deployment I want to declare a startup dependency on another Resource Archive (RAR) deployment (in my application's case, the WebSphere MQ RAR - but I have recreated this with other Resource Archives) and also have a module exclusion (in this case, on the org.apache.log4j module so that my application can use internally defined Log4J configuration).
> The jboss-deployment-structure.xml for the EAR looks like this :-
> {code:xml}
> <jboss-deployment-structure>
> <sub-deployment name="application.war">
> <dependencies>
> <module name="deployment.wmq.jmsra.rar" />
> </dependencies>
> <exclusions>
> <module name="org.apache.log4j" />
> </exclusions>
> </sub-deployment>
> </jboss-deployment-structure>
> {code}
> When I startup the EAR, the <dependencies> directive for the sub-deployment takes effect - the WAR is not started until the WebSphere MQ RAR is available. However, my <exclusions> directive is ignored and the application Log4J configuration is not used.
> If I restructure the jboss-deployment-structure.xml and remove the <dependencies> directive from the sub-deployment :-
> {code:xml}
> <jboss-deployment-structure>
> <sub-deployment name="application.war">
> <exclusions>
> <module name="org.apache.log4j" />
> </exclusions>
> </sub-deployment>
> </jboss-deployment-structure>
> {code}
> The <exclusions> directive is interpreted correctly and the application Log4J configuration is used.
> Also, if I go the other way and remove the <exclusions> directive and put the the <dependencies> directive back :-
> {code:xml}
> <jboss-deployment-structure>
> <sub-deployment name="application.war">
> <dependencies>
> <module name="deployment.wmq.jmsra.rar" />
> </dependencies>
> </sub-deployment>
> </jboss-deployment-structure>
> {code}
> The <dependencies> continues to be interpreted correctly and the WAR does not start until the dependency is available.
> It would just seem that I can't combine the two directives and have them both be interpreted correctly. I have tried changing the order of defining them in the file but that (unsurprisingly) didn't make a lot of difference.
> I have also tried this with the dependency being any other type of deployment - EAR, WAR, JAR, etc - and in those cases everything works correctly. It seems to only be an issue if the dependency is a Resource Archive.
> I've also given it a go on a recent 7.2.0 Nightly (3 Jan 2013) and it is also exhibiting the same behaviour.
> I have attached a sample application to replicate this behaviour. It uses the Apache Jackrabbit RAR (since the WebSphere MQ one is not distributable) as the Resource Archive dependency and creates 2 EAR files that are trying to use log4j to log to a file - one with just the <exclusions> directive and one with both the <dependencies> and <exclusions> directives. See the README file in the zip for more details.
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
James Perkins commented on AS7-5744:
------------------------------------
There's the problem the. They're assuming that {{java.util.logging.LogManager.getLogManager()}} will always return a {{java.util.logging.LogManager}}. In fact that's a really strange way to configure logging IMO. If it's all hard-coded why use a properties file at all?
It will also override any formatting you have defined in the logging subsystem.
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1302?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-1302:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=958311
> Upgrade log4-jboss-logmanager
> -----------------------------
>
> Key: WFLY-1302
> URL: https://issues.jboss.org/browse/WFLY-1302
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly.
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1302?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1302:
-----------------------------------------------
James Perkins <jperkins(a)redhat.com> made a comment on [bug 958311|https://bugzilla.redhat.com/show_bug.cgi?id=958311]
Upstream of log4j-jboss-logmanager contains a bug fix for serializing the ThrowableInformation correctly.
> Upgrade log4-jboss-logmanager
> -----------------------------
>
> Key: WFLY-1302
> URL: https://issues.jboss.org/browse/WFLY-1302
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly.
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Florian Beckmann (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
Florian Beckmann edited comment on AS7-5744 at 4/30/13 5:19 PM:
----------------------------------------------------------------
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
Here the code in ConfigurationManagerUtils from sphinx4.jar:
public static void configureLogger(Logger logger) {
LogManager logManager = LogManager.getLogManager();
ByteArrayOutputStream bos = new ByteArrayOutputStream();
Properties props = new Properties();
props.setProperty(".edu.cmu.sphinx.level", "FINEST");
props.setProperty("handlers", "java.util.logging.ConsoleHandler");
props.setProperty("java.util.logging.ConsoleHandler.level", "FINEST");
props.setProperty("java.util.logging.ConsoleHandler.formatter",
"edu.cmu.sphinx.util.SphinxLogFormatter");
try {
props.store(bos, "");
bos.close();
ByteArrayInputStream bis = new ByteArrayInputStream(bos.toByteArray());
logManager.readConfiguration(bis);
bis.close();
} catch (IOException ioe) {
System.err.println("Can't configure logger, using default configuration");
}
// Now we find the SphinxLogFormatter that the log manager created
// and configure it.
Handler[] handlers = logger.getHandlers();
for (Handler handler : handlers) {
handler.setFormatter(new SphinxLogFormatter());
}
}
was (Author: elessartelrunya):
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager
by James Perkins (JIRA)
James Perkins created WFLY-1302:
-----------------------------------
Summary: Upgrade log4-jboss-logmanager
Key: WFLY-1302
URL: https://issues.jboss.org/browse/WFLY-1302
Project: WildFly
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Minor
Fix For: 8.0.0.Alpha1
Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly.
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Florian Beckamann (JIRA)
[ https://issues.jboss.org/browse/AS7-5744?page=com.atlassian.jira.plugin.s... ]
Florian Beckamann commented on AS7-5744:
----------------------------------------
Actually I have none. This is Code from sphinx4.jar (http://cmusphinx.sourceforge.net), which is used in the app.
> JRE logging.properties file in a jar fails the deployment of an application
> ---------------------------------------------------------------------------
>
> Key: AS7-5744
> URL: https://issues.jboss.org/browse/AS7-5744
> Project: Application Server 7
> Issue Type: Bug
> Components: EE, Logging
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows 7 pro
> JBoss 7.1.3
> Reporter: Francois MESSIAEN
> Assignee: James Perkins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
> Attachments: logging.properties
>
>
> If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
> {noformat}
> 11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: className is null
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
> at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
> ... 6 more
> 11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
> JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
> {noformat}
> The content of the fullear.ear I use for this test is:
> * lib
> ** myejbClient.jar
> * META-INF
> ** application.xml
> ** jboss-app.xml
> ** jboss-deployment-structure.xml
> ** jboss-ejb-client.xml
> ** management-trackfolder-hornetq-jms.xml
> ** MANIFEST.MF
> * myejb.jar
> * web.war
> I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
> * org
> ** mapp
> *** ejb
> **** logging.properties
> **** Greeter.class
> * META-INF
> ** MANIFEST.MF
> The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
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
12 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-1301) Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1301?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside updated WFLY-1301:
----------------------------------
Component/s: Web (JBoss Web)
> Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
> ---------------------------------------------------------------
>
> Key: WFLY-1301
> URL: https://issues.jboss.org/browse/WFLY-1301
> Project: WildFly
> Issue Type: Bug
> Components: Web (JBoss Web), Web Services
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Alessio Soldano
>
> {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
> =========================================================================
> 16:28:15,876 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final
> 16:28:16,018 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.2.Final
> 16:28:16,068 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> 16:28:16,791 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.1.0.CR2
> 16:28:16,793 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 16:28:16,795 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.1.0.CR2
> 16:28:16,809 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.16.GA
> 16:28:16,838 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 16:28:16,861 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 16:28:16,876 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012605: Activated the following JSF Implementations: [main]
> 16:28:16,876 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
> 16:28:16,899 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
> 16:28:16,912 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 16:28:16,914 INFO [org.jboss.as.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 16:28:16,931 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.16.Final)
> 16:28:16,935 INFO [org.jboss.as.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.0.Alpha9 starting
> 16:28:16,947 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.16.Final
> 16:28:16,949 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2
> 16:28:16,953 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
> 16:28:16,956 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 16:28:17,048 INFO [io.undertow] (ServerService Thread Pool -- 47) Creating file handler for path /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/welcome-content
> 16:28:17,099 INFO [org.jboss.as.undertow] (MSC service thread 1-4) Starting server server service: service jboss.undertow.server.default-server
> 16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) Starting host default-host
> 16:28:17,105 INFO [org.jboss.as.undertow] (MSC service thread 1-3) registering handler io.undertow.server.handlers.resource.ResourceHandler@222ac389 under path '/'
> 16:28:17,120 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Alpha1
> 16:28:17,180 INFO [org.jboss.as.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
> 16:28:17,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
> 16:28:17,335 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 16:28:17,336 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /home/awhiteside/Downloads/jboss-as-8.0.0.Alpha1-SNAPSHOT/standalone/deployments
> 16:28:17,336 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
> 16:28:17,337 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
> 16:28:17,991 INFO [io.undertow.servlet] (MSC service thread 1-8) jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
> 16:28:18,115 INFO [org.jboss.as.undertow] (MSC service thread 1-8) JBAS018210: Register web context: /hawtio
> 16:28:18,143 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "hawtio.war" (runtime-name : "hawtio.war")
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 16:28:18,293 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" started in 2729ms - Started 198 of 234 services (55 services are lazy, passive or on-demand)
> 16:28:33,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "messaging-gateway.war" (runtime-name: "messaging-gateway.war")
> 16:28:35,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,398 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,400 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,401 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
> 16:28:35,437 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."messaging-gateway.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."messaging-gateway.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "messaging-gateway.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> 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]
> 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.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern.
> at org.jboss.as.webservices.metadata.model.AbstractDeployment.addEndpoint(AbstractDeployment.java:60)
> at org.jboss.as.webservices.metadata.model.JAXWSDeployment.addEndpoint(JAXWSDeployment.java:27)
> at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_POJO.processAnnotation(WSIntegrationProcessorJAXWS_POJO.java:98)
> at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:92)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> ... 5 more
> 16:28:35,442 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.deployment.unit.\"messaging-gateway.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"messaging-gateway.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"messaging-gateway.war\"
> Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /RegistrationService_V11 is already registered. Web service endpoint com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pattern."}}
> 16:28:35,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment messaging-gateway.war (runtime-name: messaging-gateway.war) in 42ms
> 16:28:35,486 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."messaging-gateway.war".PARSE
> {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
12 years, 9 months
- 1
- 0