I used to run my application on a JBoss WildFly (12.0.0.) on an EC2 instance. Also i had my databse running on a RDS instance. Everything connected very nice and it worked. But two days ago, i had to switch from my MariaDB RDS to an EC2 MariaDB (by Bitnami). I configured the connection like before, but now I get an Error during deployment like it says in title. Here's the first lines of my error stack, there are like 600 more...:
2018-06-24 09:16:40,296 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /opt/bitnami/wildfly/standalone/data/content/4b/37444aeb2e1f4f9e73b5ecfb3ee291bd830377/content
2018-06-24 09:16:40,487 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "TandemPartnerWebArchiv.war" (runtime-name: "TandemPartnerWebArchiv.war")
2018-06-24 09:16:41,804 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for ExperimentalJPADatabase
2018-06-24 09:16:41,878 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 67) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'TandemPartnerWebArchiv.war#ExperimentalJPADatabase'
2018-06-24 09:16:41,878 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 67) HHH000204: Processing PersistenceUnitInfo [
name: ExperimentalJPADatabase
...]
2018-06-24 09:16:41,932 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment TandemPartnerWebArchiv.war
2018-06-24 09:16:41,952 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'DAO' in deployment unit 'deployment "TandemPartnerWebArchiv.war"' are as follows:
java:global/TandemPartnerWebArchiv/DAO!dao.DAO
java:app/TandemPartnerWebArchiv/DAO!dao.DAO
java:module/DAO!dao.DAO
java:global/TandemPartnerWebArchiv/DAO
java:app/TandemPartnerWebArchiv/DAO
java:module/DAO
2018-06-24 09:16:42,180 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 67) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'TandemPartnerWebArchiv.war#ExperimentalJPADatabase'
2018-06-24 09:16:42,183 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 67) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
2018-06-24 09:16:42,186 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 67) Envers integration enabled? : true
2018-06-24 09:16:42,221 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 67) MSC000001: Failed to start service jboss.persistenceunit."TandemPartnerWebArchiv.war#ExperimentalJPADatabase": org.jboss.msc.service.StartException in service jboss.persistenceunit."TandemPartnerWebArchiv.war#ExperimentalJPADatabase": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:195)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:125)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:650)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:209)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97)
at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:33)
at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:27)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.workWithClassLoader(ClassLoaderServiceImpl.java:358)
at org.hibernate.internal.util.xml.XMLHelper.<init>(XMLHelper.java:26)
at org.hibernate.envers.boot.internal.EnversServiceImpl.initialize(EnversServiceImpl.java:115)
at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings(AdditionalJaxbMappingProducerImpl.java:99)
at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:288)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:848)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:875)
at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:167)
... 9 more
2018-06-24 09:16:42,223 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "TandemPartnerWebArchiv.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"TandemPartnerWebArchiv.war#ExperimentalJPADatabase\"" => "java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory"},
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.html_basic.InputHiddenTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.SelectItemTag\".WeldInstantiator",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.SelectItemsTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.DAO.START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"managed-bean.net.bootsfaces.component.radiobutton.RadioButtonInternalStateBean\".WeldInstantiator",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.RegexValidatorTag\".WeldInstantiator",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.html_basic.HtmlBasicValidator\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.html_basic.OutputLinkTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.SubviewTag\".WeldInstantiator",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.ValidateLengthTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"javax.faces.webapp.FacetTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.ActionListenerTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"org.jboss.weld.module.web.servlet.WeldInitialListener\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.ViewTag\".START",
"jboss.deployment.unit.\"TandemPartnerWebArchiv.war\".component.\"com.sun.faces.taglib.jsf_core.ValidateDoubleRangeTag\".START",
It looks like you're including a dom4j library in your deployment. You'll need to remove that dependency from your deployment.
Related
First thing, I already saw posts on it on Stackoverflow
(like this : Wildfly 9.x startet with errors: Address already in use) but no solution is working (changing the port , check if another server is running , etc) and got Jboss in a zip from http://tools.jboss.org/downloads/jbosstools/neon/4.4.0.Final.html#zips (because my eclipse marketplace didn't find it)
Bad luck this time when I start my WildFly Server on Eclipse :
23:47:12,788 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
23:47:15,449 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
23:47:15,530 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
23:47:25,711 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
23:47:26,198 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.3.4.Final
23:47:26,376 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.4.Final
23:47:26,637 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
23:47:26,654 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
23:47:26,658 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
23:47:26,945 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
23:47:26,978 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
23:47:27,100 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=4.9.4.Final
23:47:27,134 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
23:47:27,433 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
23:47:27,692 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
23:47:27,704 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
23:47:27,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.3.15.Final starting
23:47:29,761 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
23:47:29,764 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
23:47:30,400 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Progs\wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
23:47:31,056 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
23:47:31,057 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
23:47:32,848 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
23:47:32,848 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
23:47:32,978 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
23:47:32,980 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
23:47:33,057 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.18.Final
23:47:33,824 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
23:47:34,863 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
23:47:35,357 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Progs\wildfly-10.0.0.Final\standalone\deployments
23:47:35,421 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "postgresql-9.3-1103.jdbc4.jar" (runtime-name: "postgresql-9.3-1103.jdbc4.jar")
23:47:37,241 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:271)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:157)
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:237)
... 5 more
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:192)
at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243)
at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:144)
... 6 more
23:47:37,300 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
23:47:37,300 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
23:47:37,301 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
23:47:42,235 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
23:47:44,552 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.3)
23:47:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = postgresql-9.3-1103.jdbc4.jar
23:47:45,394 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind
Caused by: java.net.BindException: Address already in use: bind"}}
23:47:45,588 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "postgresql-9.3-1103.jdbc4.jar" (runtime-name : "postgresql-9.3-1103.jdbc4.jar")
23:47:45,589 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service
23:47:45,967 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
23:47:45,967 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
23:47:45,968 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 34185ms - Started 307 of 603 services (2 services failed or missing dependencies, 379 services are lazy, passive or on-demand)
What I understood with these lines is that this address is already in use.
I start this cmd command before and after the start of the server :
netstat -aon | findstr :8080
Before :
After :
I can access on the default page (localhost:8080) :
When I click on "Administration Console" , I got this :
Any solution ?
Finally , I found the answer here (Thanks Ualter Jr.) :
Check if you have service called NVIDIA Network Service running at your computer. Coincidentally this NVIDIA Service is running at the port 9990, used for the Admin console of Wildfly. In my case, it was only stop this Service and restart the Wildfly server.
I'm new to JSF and don't have an extensive experience with java on its own. Given a tutorial that provided the project files simply to download and import, I was supposed to deploy it using widlfly 10.
I haven't changed anything about the files.
I add the project to wildfly. Start the server, but the deployment is not successful. I don't know what else to tell since that's honestly all I did.
The log:
14:40:46,711 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
14:40:46,920 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:40:46,990 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
14:40:48,149 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment rhdemo-service.war
14:40:48,187 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found rhdemo-service.war in deployment directory. To trigger deployment create a file called rhdemo-service.war.dodeploy
14:40:48,208 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:40:48,222 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.4.0.Final
14:40:48,229 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.4.0.Final
14:40:48,286 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:40:48,290 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:40:48,299 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:40:48,306 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:40:48,316 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:40:48,346 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:40:48,346 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:40:48,344 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:40:48,345 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
14:40:48,420 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
14:40:48,425 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
14:40:48,505 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.6.Final
14:40:48,529 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.0.Final starting
14:40:48,535 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:40:48,546 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.21.Final
14:40:48,661 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
14:40:48,661 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
14:40:48,770 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Jaguar651w\servers\jboss\wildfly-10.1.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:40:48,796 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
14:40:48,799 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
14:40:48,914 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
14:40:49,036 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore C:\Jaguar651w\servers\jboss\wildfly-10.1.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
14:40:49,042 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:40:49,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "rhdemo-service.war" (runtime-name: "rhdemo-service.war")
14:40:49,067 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Jaguar651w\servers\jboss\wildfly-10.1.0.Final\standalone\deployments
14:40:49,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
14:40:49,308 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."rhdemo-service.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."rhdemo-service.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "rhdemo-service.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0048: Failed to process WEB-INF/lib: "/C:/Jaguar651w/servers/jboss/wildfly-10.1.0.Final/standalone/deployments/rhdemo-service.war/WEB-INF/lib/jcompany-service-1.0.0-SNAPSHOT.jar"
at org.wildfly.extension.undertow.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:131)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0048: Failed to process WEB-INF/lib: "/C:/Jaguar651w/servers/jboss/wildfly-10.1.0.Final/standalone/deployments/rhdemo-service.war/WEB-INF/lib/jcompany-service-1.0.0-SNAPSHOT.jar"
at org.wildfly.extension.undertow.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:233)
at org.wildfly.extension.undertow.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:126)
... 6 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:219)
at java.util.zip.ZipFile.<init>(ZipFile.java:149)
at java.util.jar.JarFile.<init>(JarFile.java:166)
at java.util.jar.JarFile.<init>(JarFile.java:130)
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:90)
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:77)
at org.jboss.vfs.VFS.mountZip(VFS.java:386)
at org.jboss.vfs.VFS.mountZip(VFS.java:410)
at org.wildfly.extension.undertow.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:225)
... 7 more
14:40:49,327 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
14:40:49,354 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,355 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,395 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,395 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,396 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,397 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
14:40:49,445 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
14:40:49,533 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "rhdemo-service.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"rhdemo-service.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"rhdemo-service.war\".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"rhdemo-service.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0048: Failed to process WEB-INF/lib: \"/C:/Jaguar651w/servers/jboss/wildfly-10.1.0.Final/standalone/deployments/rhdemo-service.war/WEB-INF/lib/jcompany-service-1.0.0-SNAPSHOT.jar\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0048: Failed to process WEB-INF/lib: \"/C:/Jaguar651w/servers/jboss/wildfly-10.1.0.Final/standalone/deployments/rhdemo-service.war/WEB-INF/lib/jcompany-service-1.0.0-SNAPSHOT.jar\"
Caused by: java.util.zip.ZipException: error in opening zip file"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"rhdemo-service.war\".STRUCTURE"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
14:40:49,571 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "rhdemo-service.war" (runtime-name : "rhdemo-service.war")
14:40:49,576 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."rhdemo-service.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."rhdemo-service.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "rhdemo-service.war"
14:40:49,672 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:40:49,673 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:40:49,673 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 3269ms - Started 333 of 580 services (1 services failed or missing dependencies, 393 services are lazy, passive or on-demand)
14:40:49,695 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment rhdemo-service.war (runtime-name: rhdemo-service.war) in 1ms
14:40:49,751 WARN [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
14:40:49,752 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "rhdemo-service.war" (runtime-name: "rhdemo-service.war")
14:40:49,752 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."rhdemo-service.war".STRUCTURE
14:40:54,594 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found rhdemo-service.war in deployment directory. To trigger deployment create a file called rhdemo-service.war.dodeploy
Thanks to anyone who can help
I had the same problem today. Some jar was corrupted inside my maven local repository (~/.m2 in linux mint).
Deleted it, downloaded it again and rebuilt the project. Everything seems to be fine.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
everybody, I download jbpm-6.2.0-SNAPSHOT-installer.zip from https://hudson.jboss.org/jenkins/job/jBPM/lastSuccessfulBuild/artifact/jbpm-distribution/target/ then upzip it ,ant install.demo,ant start.demo.noeclipse and changed nothing.but jbpm-console.war deployed failed.then the wildfly8.1.0 's server.log is:
2014-09-05 00:00:55,707 WARN [org.jboss.weld.Validator] (weld-worker-4) WELD-001440: Scope type #javax.enterprise.context.SessionScoped() used on injection point [BackedAnnotatedField] #Inject #SessionScoped private org.kie.workbench.common.screens.explorer.backend.server.ExplorerServiceImpl.sessionInfo
2014-09-05 00:00:55,739 WARN [org.jboss.weld.Validator] (weld-worker-4) WELD-001440: Scope type #javax.enterprise.context.SessionScoped() used on injection point [BackedAnnotatedField] #Inject #SessionScoped private org.kie.workbench.common.screens.explorer.backend.server.ExplorerServiceImpl.identity
2014-09-05 00:00:56,060 WARN [org.jboss.weld.Validator] (weld-worker-1) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.uberfire.backend.server.cdi.SystemConfigProducer$2#1e0e9173 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (#SessionScoped, #ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface.
2014-09-05 00:00:56,324 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_11]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_11]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_11]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type ProjectService with qualifiers #Default at injection point [BackedAnnotatedField] #Inject org.kie.workbench.common.services.backend.validation.JavaFileNameValidator.projectService at org.kie.workbench.common.services.backend.validation.JavaFileNameValidator.projectService(JavaFileNameValidator.java:0) at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:368)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:289)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:135)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:166)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:514)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_11]
... 3 more
2014-09-05 00:00:56,483 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jbpm-console.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type ProjectService with qualifiers #Default at injection point [BackedAnnotatedField] #Inject org.kie.workbench.common.services.backend.validation.JavaFileNameValidator.projectService at org.kie.workbench.common.services.backend.validation.JavaFileNameValidator.projectService(JavaFileNameValidator.java:0)"}}
2014-09-05 00:00:56,601 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "jbpm-console.war" (runtime-name : "jbpm-console.war")
2014-09-05 00:00:56,613 INFO [org.jboss.as.controller] (Controller Boot Thread)
JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."jbpm-console.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".WeldStartService: Failed to start service
2014-09-05 00:00:56,682 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
2014-09-05 00:00:56,691 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
2014-09-05 00:00:56,698 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 356143ms - Started 899 of 1296 services (352 services failed or missing dependencies, 112 services are lazy, passive or on-demand)
2014-09-05 00:07:12,229 INFO [org.jboss.as.controller] (management-handler-thread - 3)
JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."jbpm-console.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".WeldStartService: Failed to start service
2014-09-05 00:07:12,522 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010418: Stopped Driver service with driver-name = jbpm-console.war_org.h2.Driver_1_3
2014-09-05 00:07:12,624 INFO [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015540: Stopping service jboss.ws.endpoint."jbpm-console.war"."org.kie.remote.services.ws.command.CommandWebServiceImpl"
2014-09-05 00:07:12,685 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
2014-09-05 00:07:12,705 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
2014-09-05 00:07:12,714 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
2014-09-05 00:07:12,732 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
2014-09-05 00:07:12,742 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 66) JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service 'jbpm-console.war#org.jbpm.domain'
2014-09-05 00:07:12,821 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 68) ISPN000029: Passivating all entries to disk
2014-09-05 00:07:12,842 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 68) ISPN000030: Passivated 0 entries in 20 milliseconds
2014-09-05 00:07:12,848 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017532: Host default-host stopping
2014-09-05 00:07:12,872 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) JBAS010282: Stopped default-host cache from web container
2014-09-05 00:07:12,891 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment jbpm-console.war
2014-09-05 00:07:13,000 INFO [org.hornetq.ra] (ServerService Thread Pool -- 64) HQ151003: HornetQ resource adaptor stopped
2014-09-05 00:07:13,186 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 65) JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service 'jbpm-console.war#org.jbpm.domain'
2014-09-05 00:07:13,218 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010409: Unbound data source [java:jboss/datasources/jbpmDS]
2014-09-05 00:07:13,237 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010418: Stopped Driver service with driver-name = h2
2014-09-05 00:07:13,420 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221002: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [d78a64a1-344b-11e4-afc9-eb2cdeddc702] stopped
2014-09-05 00:07:13,443 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017521: Undertow HTTP listener default suspending
2014-09-05 00:07:13,455 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017520: Undertow HTTP listener default stopped, was bound to localhost/127.0.0.1:8080
2014-09-05 00:07:13,467 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017506: Undertow 1.0.15.Final stopping
2014-09-05 00:07:19,393 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment jbpm-console.war (runtime-name: jbpm-console.war) in 7090ms
2014-09-05 00:07:19,403 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: WildFly 8.1.0.Final "Kenny" stopped in 7100ms
Anyone can give me help?
Why do you use SNAPSHOT version? These versions might be very unstable because of their dependencies on another SNAPSHOT artifacts that are frequently changed.
Try to use version 6.1.0-Final instead. And if you really need to test version 6.2.0 because of some new features, use 6.2.0-Beta1 which should be more stable.
Apparently I have put a malformed parameterized type in my code somewhere, but the location is unknown as my IDE has not generated a warning and the stack trace does not reveal the spot where the error was encountered. Any suggestions on how to proceed would be greatly appreciated. I'm stumped.
11:04:14,476 WARN [org.jboss.weld.Event] (MSC service thread 1-3) WELD-000411: Observer method [BackedAnnotatedMethod] public org.omnifaces.VetoAnnotatedTypeExtension.processAnnotatedType(#Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using #WithAnnotations or a generic type with bounds.
11:04:14,479 DEBUG [org.jboss.weld.deployer] (MSC service thread 1-3) Discovered SYNTHETIC BeanDeploymentArchive (org.jboss.resteasy.resteasy-cdi:main.additionalClasses)
11:04:14,481 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [javax.enterprise.inject.spi.BeanManager] with qualifiers [#Default]
11:04:14,481 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [org.jboss.weld.manager.BeanManagerImpl] with qualifiers [#Default]
11:04:14,493 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class org.jboss.resteasy.cdi.ResteasyCdiExtension] with qualifiers [#Default]; application.war
11:04:14,494 DEBUG [org.jboss.weld.deployer] (MSC service thread 1-3) Discovered SYNTHETIC BeanDeploymentArchive (org.hibernate.validator.cdi:main.additionalClasses)
11:04:14,495 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [javax.enterprise.inject.spi.BeanManager] with qualifiers [#Default]
11:04:14,495 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [org.jboss.weld.manager.BeanManagerImpl] with qualifiers [#Default]
11:04:14,504 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class org.hibernate.validator.internal.cdi.ValidationExtension] with qualifiers [#Default]; application.war
11:04:14,509 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class com.sun.faces.flow.FlowDiscoveryCDIExtension] with qualifiers [#Default]; application.war
11:04:14,512 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class com.sun.faces.application.view.ViewScopeExtension] with qualifiers [#Default]; application.war
11:04:14,513 DEBUG [org.jboss.weld.deployer] (MSC service thread 1-3) Discovered SYNTHETIC BeanDeploymentArchive (org.jberet.jberet-core:main.additionalClasses)
11:04:14,514 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [javax.enterprise.inject.spi.BeanManager] with qualifiers [#Default]
11:04:14,514 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [org.jboss.weld.manager.BeanManagerImpl] with qualifiers [#Default]
11:04:14,516 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class org.jberet.creation.BatchCDIExtension] with qualifiers [#Default]; application.war
11:04:14,520 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Extension [class org.omnifaces.cdi.eager.EagerExtension] with qualifiers [#Default]; application.war
11:04:14,521 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [javax.enterprise.inject.spi.BeanManager] with qualifiers [#Default]
11:04:14,521 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000106: Bean: Built-in Bean [org.jboss.weld.manager.BeanManagerImpl] with qualifiers [#Default]
11:04:15,712 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."application.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."application.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_05]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_05]
Caused by: java.lang.reflect.MalformedParameterizedTypeException
at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.validateConstructorArguments(ParameterizedTypeImpl.java:58) [rt.jar:1.8.0_05]
at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.<init>(ParameterizedTypeImpl.java:51) [rt.jar:1.8.0_05]
at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.make(ParameterizedTypeImpl.java:92) [rt.jar:1.8.0_05]
at sun.reflect.generics.factory.CoreReflectionFactory.makeParameterizedType(CoreReflectionFactory.java:105) [rt.jar:1.8.0_05]
at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:140) [rt.jar:1.8.0_05]
at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49) [rt.jar:1.8.0_05]
at sun.reflect.generics.repository.ConstructorRepository.getParameterTypes(ConstructorRepository.java:94) [rt.jar:1.8.0_05]
at java.lang.reflect.Executable.getGenericParameterTypes(Executable.java:279) [rt.jar:1.8.0_05]
at java.lang.reflect.Method.getGenericParameterTypes(Method.java:268) [rt.jar:1.8.0_05]
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedMethod.initParameters(BackedAnnotatedMethod.java:44)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedMethod.initParameters(BackedAnnotatedMethod.java:27)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedCallable.<init>(BackedAnnotatedCallable.java:34)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedMethod.<init>(BackedAnnotatedMethod.java:38)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedMethod.of(BackedAnnotatedMethod.java:32)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.computeValue(BackedAnnotatedType.java:193)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.computeValue(BackedAnnotatedType.java:186)
at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:35)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$EagerlyInitializedLazyValueHolder.<init>(BackedAnnotatedType.java:154)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.<init>(BackedAnnotatedType.java:186)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.<init>(BackedAnnotatedType.java:186)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.<init>(BackedAnnotatedType.java:66)
at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.of(BackedAnnotatedType.java:47)
at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.load(ClassTransformer.java:83)
at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.load(ClassTransformer.java:80)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3524)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2317)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195)
at com.google.common.cache.LocalCache.get(LocalCache.java:3934)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3938)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4821)
at org.jboss.weld.util.cache.LoadingCacheUtils.getCacheValue(LoadingCacheUtils.java:52)
at org.jboss.weld.util.cache.LoadingCacheUtils.getCastCacheValue(LoadingCacheUtils.java:80)
at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:175)
at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:194)
at org.jboss.weld.bootstrap.BeanDeployer.loadAnnotatedType(BeanDeployer.java:119)
at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:96)
at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:62)
at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_05]
... 3 more
11:04:15,744 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "application.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"application.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"application.war\".WeldStartService: Failed to start service
Caused by: java.lang.reflect.MalformedParameterizedTypeException"}}
11:04:15,760 ERROR [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "application.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"application.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"application.war\".WeldStartService: Failed to start service
Caused by: java.lang.reflect.MalformedParameterizedTypeException"}}
11:04:15,792 DEBUG [org.wildfly.jberet] (MSC service thread 1-7) Removing batch environment; ModuleClassLoader for Module "deployment.application.war:main" from Service Module Loader
11:04:15,816 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 25) JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service 'application.war#primary'
11:04:15,817 DEBUG [org.hibernate.internal.SessionFactoryImpl] (ServerService Thread Pool -- 25) HHH000031: Closing
11:04:15,817 DEBUG [org.hibernate.cache.infinispan.InfinispanRegionFactory] (ServerService Thread Pool -- 25) Stop region factory
11:04:15,817 DEBUG [org.hibernate.cache.infinispan.InfinispanRegionFactory] (ServerService Thread Pool -- 25) Clear region references
11:04:15,840 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 25) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.2.Final
11:04:16,177 DEBUG [org.infinispan.interceptors.InterceptorChain] (ServerService Thread Pool -- 25) Interceptor chain size: 6
11:04:16,177 DEBUG [org.infinispan.interceptors.InterceptorChain] (ServerService Thread Pool -- 25) Interceptor chain is:
>> org.infinispan.interceptors.InvocationContextInterceptor
>> org.infinispan.interceptors.CacheMgmtInterceptor
>> org.infinispan.interceptors.NotificationInterceptor
>> org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor
>> org.infinispan.interceptors.EntryWrappingInterceptor
>> org.infinispan.interceptors.CallInterceptor
11:04:16,183 DEBUG [org.infinispan.jmx.JmxUtil] (ServerService Thread Pool -- 25) Object name jboss.infinispan:type=Cache,name="local-query(local)",manager="hibernate",component=Cache already registered
11:04:16,184 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 25) ISPN000031: MBeans were successfully registered to the platform MBean server.
11:04:16,190 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 25) JBAS010281: Started local-query cache from hibernate container
11:04:16,192 DEBUG [org.infinispan.CacheImpl] (ServerService Thread Pool -- 25) Started cache local-query on null
11:04:16,200 DEBUG [org.hibernate.service.internal.AbstractServiceRegistryImpl] (ServerService Thread Pool -- 25) Implicitly destroying ServiceRegistry on de-registration of all child ServiceRegistries
11:04:16,200 DEBUG [org.hibernate.boot.registry.internal.BootstrapServiceRegistryImpl] (ServerService Thread Pool -- 25) Implicitly destroying Boot-strap registry on de-registration of all child ServiceRegistries
11:04:16,201 DEBUG [org.hibernate.jpa.internal.EntityManagerFactoryRegistry] (ServerService Thread Pool -- 25) Remove: name=application.war#primary
11:04:16,202 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment application.war
11:04:16,297 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 25) JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service 'application.war#primary'
11:04:16,302 DEBUG [org.jboss.as.clustering.infinispan.subsystem] (ServerService Thread Pool -- 25) local-query cache configuration stopped
11:04:16,301 DEBUG [org.jboss.as.clustering.infinispan.subsystem] (ServerService Thread Pool -- 22) timestamps cache configuration stopped
11:04:16,302 DEBUG [org.jboss.as.clustering.infinispan.subsystem] (ServerService Thread Pool -- 24) entity cache configuration stopped
11:04:16,303 DEBUG [org.infinispan.manager.DefaultCacheManager] (MSC service thread 1-4) Stopping cache manager ISPN on null
11:04:16,306 DEBUG [org.infinispan.CacheImpl] (MSC service thread 1-4) Stopping cache local-query on null
11:04:16,309 DEBUG [org.infinispan.transaction.TransactionTable] (MSC service thread 1-4) Wait for on-going transactions to finish for 30 seconds.
11:04:16,310 DEBUG [org.infinispan.transaction.TransactionTable] (MSC service thread 1-4) All transactions terminated
11:04:16,311 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) JBAS010282: Stopped local-query cache from hibernate container
11:04:16,317 DEBUG [org.jboss.as.clustering.infinispan.subsystem] (MSC service thread 1-4) hibernate cache container stopped
11:04:16,330 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment application.war (runtime-name: application.war) in 555ms
UPDATE:
The MalformedParameterizedTypeException is
"Thrown when a semantically malformed parameterized type is encountered by a reflective method that needs to instantiate it. For example, if the number of type arguments to a parameterized type is wrong."
I was waaay off. There was no problem with my code at all. The problem was that my project had a dependency that was not compatible with a JEE module installed on the server.
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<!--
scope=compile prevents
Warning:java: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size':
class file for javax.validation.constraints.Size not found
-->
<scope>compile</scope>
</dependency>
The problem started when Intellij (but not Maven) began to issue warnings, such as the one above, when compiling. The following change eliminated the MalformedParameterizedTypeException problem but reintroduced the annoying Intellij warning.
<scope>provided</scope>
JetBrains support created a new issue in its bug tracker: http://youtrack.jetbrains.com/issue/IDEA-127569
I am getting following error while deploying our EAR to JBoss AS 7.1 as a standalone deployment. Please see the server error log and help me out in what I need to do for it to start functioning correctly. Thank You
12:21:47,165 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
12:21:47,167 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
12:21:47,211 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
12:21:47,211 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
12:21:47,212 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
12:21:47,215 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
12:21:47,219 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013100: Current PicketBox version=4.0.7.Final
12:21:47,232 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
12:21:47,250 INFO [org.jboss.as.connector] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
12:21:47,262 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:21:47,328 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:21:47,467 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
12:21:47,624 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8085
12:21:47,658 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory D:\jboss-as-7.1.1.Final\standalone\deployments
12:21:47,659 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:4447
12:21:47,660 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on /127.0.0.1:9999
12:21:47,808 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:21:48,018 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.ojdbc14-10_2_0_5_jar (missing) dependents: [service jboss.data-source.java:/jdbc/DefaultDS]
12:21:48,036 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "Shrisurance.ear"
12:21:54,210 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: Failed to process phase STRUCTURE of deployment "Shrisurance.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to get manifest for deployment "/D:/jboss-as-7.1.1.Final/bin/content/Shrisurance.ear/Shrisurance.war"
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:73) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.io.IOException: invalid header field
at java.util.jar.Attributes.read(Attributes.java:393) [rt.jar:1.6.0_25]
at java.util.jar.Manifest.read(Manifest.java:182) [rt.jar:1.6.0_25]
at java.util.jar.Manifest.<init>(Manifest.java:52) [rt.jar:1.6.0_25]
at org.jboss.vfs.VFSUtils.readManifest(VFSUtils.java:216) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFSUtils.getManifest(VFSUtils.java:199) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:69) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 6 more
12:21:54,257 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:21:54,257 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Shrisurance.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Shrisurance.ear\""}}
12:21:54,258 ERROR [org.jboss.as] (MSC service thread 1-5) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7927ms - Started 136 of 215 services (3 services failed or missing dependencies, 74 services are passive or on-demand)
12:21:54,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Shrisurance.ear in 7ms
12:21:54,267 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: Failed to process phase STRUCTURE of deployment "Shrisurance.ear"
12:21:54,277 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Shrisurance.ear\""}}}}
12:22:02,431 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011942: Stopping OSGi Framework
Case 1 : Looking from log
New missing/unsatisfied dependencies:
service jboss.jdbc-driver.ojdbc14-10_2_0_5_jar
It is found that you are using ojdbc14 version of jar. It is for JDK 1.4. If you are using JDK 1.4+ version then use ojdbc14+ driver. Latest Oracle Driver Download Link
Modify module.xml ( # jboss-as-web-7.0.2.Final\modules\com\oracle\ojdbcXXX\main )
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.oracle.ojdbcXXX">
<resources>
<resource-root path="ojdbcXXX.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>
Add ojdbcXXX.jar ( # jboss-as-web-7.0.2.Final\modules\com\oracle\ojdbcXXX\main )
Define Data-source in standalone.xml
<datasource jndi-name="java:/OracleDS" pool-name="OracleDS">
<connection-url>jdbc:oracle:thin:#host:port:SID</connection-url>
<driver>ojdbcXXX</driver>
</datasource>
<drivers>
<driver name="ojdbcXXX" module="com.oracle.ojdbcXXX">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
Case 2 : Include other deployments in EAR
JBoss find that dependency spurious. If your EAR contains other deployments like .jar or.war then you can try below :-
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
</jboss-deployment-structure>