[JBoss JIRA] (WFLY-1301) Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1301?page=com.atlassian.jira.plugin.... ]
Alessio Soldano edited comment on WFLY-1301 at 5/2/13 4:34 AM:
---------------------------------------------------------------
You should not deploy a war with Metro webservices-rt.jar embedded in it. JBoss AS / WildFly already comes with a compliant WS stack in it.
This said, if you really need/want to do so, you might want to try disabling the webservices susbsystem using a jboss-deployment-structure.xml as follows:
{code}
<?xml version="1.0" encoding="ISO-8859-1"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<exclude-subsystems>
<subsystem name="webservices" />
<subsystem name="weld" /> <!-- Prevent WELD-000070 failure -->
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
{code}
Also check https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 for further info.
was (Author: asoldano):
You should not deploy a war with Metro webservices-rt.jar embedded in it. JBoss AS already comes with a compliant WS stack in it.
This said, if you really need/want to do so, you might want to try disabling the webservices susbsystem using a jboss-deployment-structure.xml as follows:
{code}
<?xml version="1.0" encoding="ISO-8859-1"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<exclude-subsystems>
<subsystem name="webservices" />
<subsystem name="weld" /> <!-- Prevent WELD-000070 failure -->
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
{code}
Also check https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 for further info.
> 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
[JBoss JIRA] (WFLY-1301) Cannot deploy WAR with Metro webservices-rt.jar in WEB-INF/lib.
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1301?page=com.atlassian.jira.plugin.... ]
Alessio Soldano resolved WFLY-1301.
-----------------------------------
Resolution: Rejected
You should not deploy a war with Metro webservices-rt.jar embedded in it. JBoss AS already comes with a compliant WS stack in it.
This said, if you really need/want to do so, you might want to try disabling the webservices susbsystem using a jboss-deployment-structure.xml as follows:
{code}
<?xml version="1.0" encoding="ISO-8859-1"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<exclude-subsystems>
<subsystem name="webservices" />
<subsystem name="weld" /> <!-- Prevent WELD-000070 failure -->
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
{code}
Also check https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 for further info.
> 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
[JBoss JIRA] (JBJCA-637) DataSource support
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBJCA-637?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBJCA-637:
-----------------------------------------------
Tom Fonteyne <tfonteyn(a)redhat.com> made a comment on [bug 957175|https://bugzilla.redhat.com/show_bug.cgi?id=957175]
@John Doyle: "if a datasource class is defined first, then fallback to java.sql.Driver - the opposite of today."
This bit is incorrect: "the opposite of today."
The situation "today" is that the datasource class can *never* be used in EAP for the simple fact that all major vendors driver have the driver class preset.
@Jesper Pedersen: "
The "datasource-class" element is there in order to support JDBC like drivers which doesn't implement the java.sql.Driver class."
Could you please provide an example ? I mean do you have such a non-driver that can be deployed to EAP so we can see the functionality working as you state ?
> DataSource support
> ------------------
>
> Key: JBJCA-637
> URL: https://issues.jboss.org/browse/JBJCA-637
> Project: IronJacamar
> Issue Type: Task
> Components: Common, Deployer, JDBC
> Reporter: Jesper Pedersen
> Assignee: Jesper Pedersen
> Fix For: 1.0.2.Final, 1.1.0.Alpha1
>
>
> We should support <datasource> deployments based on a javax.sql.DataSource instance.
> Add <datasource-class> to <datasource> and <driver> as optional.
--
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
[JBoss JIRA] (JBJCA-1014) DataSource class is never picked for establishing connection, driverClass is always picked.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1014?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBJCA-1014:
------------------------------------------------
Tom Fonteyne <tfonteyn(a)redhat.com> made a comment on [bug 957175|https://bugzilla.redhat.com/show_bug.cgi?id=957175]
@John Doyle: "if a datasource class is defined first, then fallback to java.sql.Driver - the opposite of today."
This bit is incorrect: "the opposite of today."
The situation "today" is that the datasource class can *never* be used in EAP for the simple fact that all major vendors driver have the driver class preset.
@Jesper Pedersen: "
The "datasource-class" element is there in order to support JDBC like drivers which doesn't implement the java.sql.Driver class."
Could you please provide an example ? I mean do you have such a non-driver that can be deployed to EAP so we can see the functionality working as you state ?
> DataSource class is never picked for establishing connection, driverClass is always picked.
> -------------------------------------------------------------------------------------------
>
> Key: JBJCA-1014
> URL: https://issues.jboss.org/browse/JBJCA-1014
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 1.0.13.Final
> Environment: Windows-7, JBoss AS-7.1, SQL Server, JDK-1.7.0
> Reporter: Himanshu Bhardwaj
> Assignee: Jesper Pedersen
> Labels: JDBC
>
> Use Case: Implemented a custom datasource for some extension purposes over sqljdbc4.jar (JDBC-4 compliant).
> Now when configuring the datasource, the module was loaded successfully, the configuration used in standalone.xml:
> <datasource jta="true" jndi-name="java:jboss/datasources/ejb/testdbjndi" pool-name="test-cluster-Pool" enabled="true" use-java-context="true" use-ccm="false">
> <connection-url>jdbc:sqlserver://localhost:1433;databaseName=cm-6.5;</connection-url>
> <datasource-class>com.himanshu.jdbcdriver.datasource.DataSource</datasource-class>
> <connection-property name="serverName">
> <!-- IP of the database server -->
> </connection-property>
> <driver>test-jdbc</driver>
> <new-connection-sql>SET DATEFIRST 1</new-connection-sql>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>100</max-pool-size>
> <prefill>false</prefill>
> </pool>
> <security>
> <user-name>sa</user-name>
> <password>sa</password>
> </security>
> <statement>
> <prepared-statement-cache-size>32</prepared-statement-cache-size>
> <share-prepared-statements>true</share-prepared-statements>
> </statement>
> </datasource>
> <driver name="test-jdbc" module="com.himanshu.jdbc"/>
> Now on doing testing the connections were successfully established and queries were getting executed.
> But it turns out the my custom datasource class is not used, rather the connection is made via driverClass, DriverManager.getConnection() kind of method.
> On debugging code for ironjacamar:
>
> org.jboss.ironjacamar
> ironjacamar-jdbc
> 1.0.13.Final-redhat-1
> On looking code for "org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory", it turns out that both the driverClass property (META-INF/services/java.sql.driver file) and dataSourceClass property (from standalone.xml) is read.
> Now the way connection is made is bit confusing here.
> Looking into method: private LocalManagedConnection getLocalManagedConnection(Properties props, Properties copy); in class
> "LocalManagedConnectionFactory"
> private LocalManagedConnection getLocalManagedConnection(Properties props, Properties copy)
> throws ResourceException
> {
> Connection con = null;
> try
> {
> if (driverClass != null)
> {
> String url = getConnectionURL();
> Driver d = getDriver(url);
> con = d.connect(url, copy);
> if (con == null)
> throw new ResourceException("Wrong driver class [" + d.getClass() + "] for this connection URL [" +
> url + "]");
> }
> else
> {
> DataSource d = getDataSource();
> con = d.getConnection(copy.getProperty("user"), copy.getProperty("password"));
> if (con == null)
> throw new ResourceException("Unable to create connection from datasource");
> }
> return new LocalManagedConnection(this, con, props, transactionIsolation, preparedStatementCacheSize);
> }
> catch (Throwable e)
> {
> if (con != null)
> {
> try
> {
> con.close();
> }
> catch (Throwable ignored)
> {
> // Ignore
> }
> }
> throw new ResourceException("Could not create connection", e);
> }
> }
> Now the if-else block condition here is difficult to understand:
> If I have driverClass available then all the connections are made via driverClass property, even if I mention datasourceClass or not.
> This is because the first if condition always checks for driverClass the dataSourceClass check never executes.
> So the question is how this can be avoided, becuase the DriverClass is picked automatically from the java.sql.driver file (being JDBC-4 compliant).
> If there is no configuration for the same for giving priority to datasource class or explicitly setting the driver class to null, then definitely something's amiss.
--
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
[JBoss JIRA] (WFLY-827) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance
by Brand Neu (JIRA)
[ https://issues.jboss.org/browse/WFLY-827?page=com.atlassian.jira.plugin.s... ]
Brand Neu commented on WFLY-827:
--------------------------------
Your workaround is ok for now!
Further enhancement: Jboss(Wildfly)-Log should contain not only the above NullPointer-Exception, but also a hint the problem and/or link to CDI.
> NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance
> ---------------------------------------------------------------------------
>
> Key: WFLY-827
> URL: https://issues.jboss.org/browse/WFLY-827
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Brand Neu
> Assignee: Scott Marlow
> Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm
>
>
> Webproject with ManagedBean contains following PersistenceContext:
> @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED)
> WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions.
--
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
[JBoss JIRA] (WFLY-742) Create a dummy InitialDirContext to allow for testing.
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-742?page=com.atlassian.jira.plugin.s... ]
Emmanuel Hugonnet commented on WFLY-742:
----------------------------------------
Using the ApcheDS JUnit runner ?
> Create a dummy InitialDirContext to allow for testing.
> ------------------------------------------------------
>
> Key: WFLY-742
> URL: https://issues.jboss.org/browse/WFLY-742
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Fix For: Awaiting Volunteers
>
>
> The testing of any LDAP configuration brings in the dependency on an LDAP server, this is fine for major QA testing but not so fine for the testsuite run in multiple environments.
> This task is to either find an existing implementation we can use or to implement a dummy InitialDirContext that can simulate the connection to LDAP allowing testing of the LDAP 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
[JBoss JIRA] (WFLY-742) Create a dummy InitialDirContext to allow for testing.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-742?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on WFLY-742:
---------------------------------------
Actually this one is probably out of date now, we have already brought in Apache DS for testing as we have a number of Kerberos use cases in the test suite - we can probably now just make use of that instead of needing a dummy implementation.
> Create a dummy InitialDirContext to allow for testing.
> ------------------------------------------------------
>
> Key: WFLY-742
> URL: https://issues.jboss.org/browse/WFLY-742
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Fix For: Awaiting Volunteers
>
>
> The testing of any LDAP configuration brings in the dependency on an LDAP server, this is fine for major QA testing but not so fine for the testsuite run in multiple environments.
> This task is to either find an existing implementation we can use or to implement a dummy InitialDirContext that can simulate the connection to LDAP allowing testing of the LDAP 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