[JBoss JIRA] (WFLY-1151) JBoss uses static Hibernate module instead of Hibernate jars included in deployment
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1151?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-1151:
-------------------------------
Fix Version/s: 8.0.0.Alpha2
> JBoss uses static Hibernate module instead of Hibernate jars included in deployment
> -----------------------------------------------------------------------------------
>
> Key: WFLY-1151
> URL: https://issues.jboss.org/browse/WFLY-1151
> Project: WildFly
> Issue Type: Feature Request
> Components: Class Loading, JPA / Hibernate
> Environment: JBoss 7.1.1.Final & Hibernate 4.1.5.SP1 on Mac OSX 10.7/10.8
> SQL Server 2008 on Windows 7 virtual
> Reporter: Kuthair Habboush
> Assignee: Scott Marlow
> Labels: classloader, hibernate, jboss, persistence.xml
> Fix For: 8.0.0.Alpha2
>
> Attachments: hibernate-test.zip, persistence.xml
>
>
> JBoss is loading Hibernate 4.0.1.Final (ships with) instead of the version specified in my Maven POM file and embedded in WAR archive, version: 4.1.5.SP1.
> This ONLY occurs when I have a Persistence Unit setup in my WAR file in directory: resources/META-INF.
> If I rename persistence.xml to persistence.xml.old, JBoss loads the correct version: Hibernate 4.1.5.SP1.
> I have a sample project.
--
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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-50) Management Console - LDAP authentication fails
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-50?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse resolved WFLY-50.
----------------------------------
Resolution: Out of Date
> Management Console - LDAP authentication fails
> ----------------------------------------------
>
> Key: WFLY-50
> URL: https://issues.jboss.org/browse/WFLY-50
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml
> Reporter: narayana b
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.Alpha2
>
>
> 1) security realms
> <!-- nari start -->
> <security-realm name="my_Ldap_Realm">
> <authentication>
> <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com">
> <username-filter attribute="sAMAccountName"/>
> <!--
> <advanced-filter filter="(sAMAccountName={0})"/> -->
> </ldap>
> </authentication>
> </security-realm>
> <!-- nari end -->
> 2) outbound connections
> <!--nari start -->
> <outbound-connections>
> <ldap name="my_Ldap_Connection"
> url="ldap://localhost:10389/"
> search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" />
> </outbound-connections>
> <!--nari end -->
> 3) Management console info config
> <!-- nari -->
> <native-interface security-realm="my_Ldap_Realm">
> <socket-binding native="management-native"/>
> </native-interface>
> <http-interface security-realm="my_Ldap_Realm">
> <socket-binding http="management-http"/>
> <!-- nari disabled [http] and enabled [https]
> <socket-binding https="management-console-https"/> -->
>
> </http-interface>
> <!-- nari end -->
--
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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1303?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside commented on WFLY-1303:
---------------------------------------
Just wanted to point out that Tomcat 7 disables automatic scanning of @HandlesTypes when either metadata-complete="true" or the servlet version is < 3.0.
http://stackoverflow.com/questions/7798783/tomcat-7-unable-to-load-class-...
> 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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-218) Update add-user utility to allow overrides of property file name.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-218?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated WFLY-218:
----------------------------------
Priority: Critical (was: Major)
> Update add-user utility to allow overrides of property file name.
> -----------------------------------------------------------------
>
> Key: WFLY-218
> URL: https://issues.jboss.org/browse/WFLY-218
> Project: WildFly
> Issue Type: Enhancement
> Components: Domain Management, Scripts
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.Alpha2
>
>
--
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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-1346) avoid "transaction is not active" error by having CMTTxInterceptor.endTransaction check transaction status
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1346?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-1346:
-------------------------------
Forum Reference: https://community.jboss.org/thread/228534, https://community.jboss.org/thread/228598 (was: https://community.jboss.org/thread/228534)
> avoid "transaction is not active" error by having CMTTxInterceptor.endTransaction check transaction status
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1346
> URL: https://issues.jboss.org/browse/WFLY-1346
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 8.0.0.Alpha1
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Attachments: alreadyRolledbackError.txt, server.zip
>
>
> See attached log for example exception that could be avoided if we change CMTTxInterceptor.endTransaction() to check the transaction status.
--
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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-1303) metadata-complete="true" not honored for ServletContainerInitializer's annotated with @HandlesTypes
by Aaron Whiteside (JIRA)
[ https://issues.jboss.org/browse/WFLY-1303?page=com.atlassian.jira.plugin.... ]
Aaron Whiteside commented on WFLY-1303:
---------------------------------------
Anyway to override this?
> 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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-1239) A Negotiated HTTP Authenticator
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1239?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved WFLY-1239.
------------------------------------
Resolution: Out of Date
WildFly has moved to Undertow which already supports multiple authentication mechanisms.
> A Negotiated HTTP Authenticator
> -------------------------------
>
> Key: WFLY-1239
> URL: https://issues.jboss.org/browse/WFLY-1239
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: Common_Authentication
>
> Historically we have become constrained by an assumption that there should be a single authentication mechanism assigned to a web application.
> The HTTP specification however allows for multiple mechanisms to be used in parallel - this task is to investigate the feasibility of writing a single authenticator that is compatible with both JBoss Web and the Sun HTTP server used within AS7 to support a negotiated authentication using a single authenticator backed by a CallbackHandler based realm.
> The most common example is fallback from SPNEGO to a username / password based mechanism but for domain management we have also a case of trying to use CLIENT-CERT authentication first and then fallback if that is not possible.
--
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
13 years, 1 month
- 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:
---------------------------------------
Is there anyway to stop Wildfly from trying to initialize/load every Servlet Listener in a war? In short disable the automatic class scanning for servlets and listeners?
> 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
> Fix For: 8.0.0.Alpha1
>
>
> 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
13 years, 1 month
- 1
- 0
[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann commented on WFLY-1406:
------------------------------------------
I'm just leaving the office (in Germany). I'll try with Alpha1 tomorrow.
> Hibernate cannot process package-info.java any more
> ---------------------------------------------------
>
> Key: WFLY-1406
> URL: https://issues.jboss.org/browse/WFLY-1406
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Scott Marlow
> Attachments: server.log
>
>
> I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError:
> "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below.
> Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1:
> @XmlAccessorType(FIELD)
> @Vetoed
> package de.shop.artikelverwaltung.domain;
> import static javax.xml.bind.annotation.XmlAccessType.FIELD;
> import javax.enterprise.inject.Vetoed;
> import javax.xml.bind.annotation.XmlAccessorType;
> The stacktrace:
> ...
> 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21]
> at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final]
> ... 28 more
--
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
13 years, 1 month
- 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 commented on WFLY-1301:
---------------------------------------
Hi Alessio, that gets me further.. but my WAR still fails to deploy because Wildfly is trying to auto deploy servlets embedded in metro/jersey jars. Is there anyway to disable this functionality?
{code}
11:45:35,208 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) 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:194)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75)
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:166)
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:161)
... 6 more
11:45:35,211 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "messaging-gateway.war")]) - failure description: {"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"}}
11:45:35,211 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"}}
{code}
> 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
13 years, 1 month
- 1
- 0