3 Replies Latest reply on Aug 7, 2018 3:52 PM by Greg Jewell

    Errors when running project on Wildfly

    Teo Kac Newbie

      Hello. I have a problem and can't solve it in any way. Please if anybody can help me. When I run my EAR project on server this happens:

       

      11:43:59,065 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.1.Final

      11:43:59,527 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1

      11:43:59,690 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) starting

      11:44:01,893 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

      11:44:01,923 INFO  [org.wildfly.security] (ServerService Thread Pool -- 18) ELY00001: WildFly Elytron version 1.1.6.Final

      11:44:01,941 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 3) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

      11:44:02,039 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found FitnesEAR.ear in deployment directory. To trigger deployment create a file called FitnesEAR.ear.dodeploy

      11:44:02,218 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

      11:44:02,237 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.5.4.Final

      11:44:02,249 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.5.4.Final

      11:44:02,342 INFO  [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.5.Final

      11:44:02,360 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)

      11:44:02,380 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 47) WFLYRS0016: RESTEasy version 3.0.24.Final

      11:44:02,406 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 63) WFLYSEC0002: Activating Security Subsystem

      11:44:02,393 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 64) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.

      11:44:02,408 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 56) WFLYNAM0001: Activating Naming Subsystem

      11:44:02,410 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0001: Activating Infinispan subsystem.

      11:44:02,412 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 66) WFLYWS0002: Activating WebServices Extension

      11:44:02,418 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]

      11:44:02,459 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 44) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors

      11:44:02,461 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 46) WFLYIIOP0001: Activating IIOP Subsystem

      11:44:02,544 INFO  [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final

      11:44:02,601 INFO  [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)

      11:44:02,617 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.18.Final starting

      11:44:02,659 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2

      11:44:02,665 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service

      11:44:02,671 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

      11:44:02,881 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) 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.

      11:44:02,883 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) 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.

      11:44:03,061 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0014: Creating file handler for path 'C:\AISV\wildfly-11.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

      11:44:03,103 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.

      11:44:03,122 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting

      11:44:03,280 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

      11:44:03,669 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: EJB subsystem suspension complete

      11:44:03,718 INFO  [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none

      11:44:03,730 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.

      11:44:03,785 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore C:\AISV\wildfly-11.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost

      11:44:03,823 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\AISV\wildfly-11.0.0.Final\standalone\deployments

      11:44:03,854 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "sqljdbc4.jar" (runtime-name: "sqljdbc4.jar")

      11:44:03,854 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "FitnesEAR.ear" (runtime-name: "FitnesEAR.ear")

      11:44:03,971 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\AISV\wildfly-11.0.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\AISV\wildfly-11.0.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\AISV\wildfly-11.0.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\AISV\wildfly-11.0.0.Final\standalone\data\activemq\paging)

      11:44:04,029 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

      11:44:04,103 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221013: Using NIO Journal

      11:44:04,314 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE

      11:44:04,319 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP

      11:44:04,327 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

      11:44:04,329 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP

      11:44:04,440 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started

      11:44:04,530 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "Fitnes.war")

      11:44:04,531 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "FitnesEJB.jar")

      11:44:04,715 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443

      11:44:04,849 INFO  [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)

      11:44:05,205 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

      11:44:05,195 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

      11:44:05,194 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

      11:44:05,190 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

      11:44:05,372 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)

      11:44:05,452 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = sqljdbc4.jar

      11:44:05,626 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221007: Server is now live

      11:44:05,626 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.5.jbossorg-008 [default, nodeID=e8166652-6ff6-11e8-bfa9-3ca067c408fd]

      11:44:05,737 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

      11:44:05,777 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final

      11:44:05,787 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory

      11:44:05,797 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.ExpiryQueue

      11:44:05,824 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221003: Deploying queue jms.queue.DLQ

      11:44:05,930 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0007: Registered connection factory java:/JmsXA

      11:44:06,132 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-5) Resource adaptor started

      11:44:06,133 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatoractivemq-ra

      11:44:06,138 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]

      11:44:06,139 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

      11:44:06,171 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment FitnesEAR.ear

      11:44:06,281 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.5.Final

      11:44:06,458 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started client-mappings cache from ejb container

      11:44:06,484 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment FitnesEJB.jar

      11:44:06,487 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment Fitnes.war

      11:44:06,499 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'ClaniBean' in deployment unit 'subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/Fitnes/ClaniBean!si.um.jpa3.ejb.ClaniBeanLocal

      java:app/Fitnes/ClaniBean!si.um.jpa3.ejb.ClaniBeanLocal

      java:module/ClaniBean!si.um.jpa3.ejb.ClaniBeanLocal

      java:global/FitnesEAR/Fitnes/ClaniBean

      java:app/Fitnes/ClaniBean

      java:module/ClaniBean

       

       

      11:44:06,503 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'VajeBean' in deployment unit 'subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/Fitnes/VajeBean!si.um.jpa3.ejb.VajeBeanLocal

      java:app/Fitnes/VajeBean!si.um.jpa3.ejb.VajeBeanLocal

      java:module/VajeBean!si.um.jpa3.ejb.VajeBeanLocal

      java:global/FitnesEAR/Fitnes/VajeBean

      java:app/Fitnes/VajeBean

      java:module/VajeBean

       

       

      11:44:06,503 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TrenerjiBean' in deployment unit 'subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/Fitnes/TrenerjiBean!si.um.jpa3.ejb.TrenerjiBeanLocal

      java:app/Fitnes/TrenerjiBean!si.um.jpa3.ejb.TrenerjiBeanLocal

      java:module/TrenerjiBean!si.um.jpa3.ejb.TrenerjiBeanLocal

      java:global/FitnesEAR/Fitnes/TrenerjiBean

      java:app/Fitnes/TrenerjiBean

      java:module/TrenerjiBean

       

       

      11:44:06,503 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'MeritveBean' in deployment unit 'subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/Fitnes/MeritveBean!si.um.jpa3.ejb.MeritveBeanLocal

      java:app/Fitnes/MeritveBean!si.um.jpa3.ejb.MeritveBeanLocal

      java:module/MeritveBean!si.um.jpa3.ejb.MeritveBeanLocal

      java:global/FitnesEAR/Fitnes/MeritveBean

      java:app/Fitnes/MeritveBean

      java:module/MeritveBean

       

       

      11:44:06,669 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'ObvescanjeBean' in deployment unit 'subdeployment "FitnesEJB.jar" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/FitnesEJB/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanLocal

      java:app/FitnesEJB/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanLocal

      java:module/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanLocal

      java:global/FitnesEAR/FitnesEJB/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanRemote

      java:app/FitnesEJB/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanRemote

      java:module/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanRemote

      java:jboss/exported/FitnesEAR/FitnesEJB/ObvescanjeBean!si.um.feri.aiv.obvescanje.ObvescanjeBeanRemote

       

       

      11:44:06,669 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'ITMBean' in deployment unit 'subdeployment "FitnesEJB.jar" of deployment "FitnesEAR.ear"' are as follows:

       

       

      java:global/FitnesEAR/FitnesEJB/ITMBean!si.um.feri.aiv.izracuni.ITMBeanRemote

      java:app/FitnesEJB/ITMBean!si.um.feri.aiv.izracuni.ITMBeanRemote

      java:module/ITMBean!si.um.feri.aiv.izracuni.ITMBeanRemote

      java:jboss/exported/FitnesEAR/FitnesEJB/ITMBean!si.um.feri.aiv.izracuni.ITMBeanRemote

      java:global/FitnesEAR/FitnesEJB/ITMBean!si.um.feri.aiv.izracuni.ITMBeanLocal

      java:app/FitnesEJB/ITMBean!si.um.feri.aiv.izracuni.ITMBeanLocal

      java:module/ITMBean!si.um.feri.aiv.izracuni.ITMBeanLocal

       

       

      11:44:06,711 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.4.3 (Final)

      11:44:06,917 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)

      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)

      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

      at java.lang.Thread.run(Thread.java:748)

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0041: Component class si.um.jpa3.ejb.ClaniBean for component ClaniBean has errors:

      WFLYJPA0033: Can't find a persistence unit named null in subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"

      at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:157)

      at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54)

      at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:186)

      at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:143)

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)

      ... 5 more

       

       

      11:44:07,070 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "FitnesEAR.ear")]) - failure description: {

          "WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of subdeployment \"Fitnes.war\" of deployment \"FitnesEAR.ear\"

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0041: Component class si.um.jpa3.ejb.ClaniBean for component ClaniBean has errors:

      WFLYJPA0033: Can't find a persistence unit named null in subdeployment \"Fitnes.war\" of deployment \"FitnesEAR.ear\""},

          "WFLYCTL0412: Required services that are not installed:" => [

              "jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".jndiDependencyService",

              "jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".beanmanager",

              "jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".deploymentCompleteService"

          ],

          "WFLYCTL0180: Services with missing/unavailable dependencies" => [

              "jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".beanmanager]",

              "jboss.deployment.unit.\"FitnesEAR.ear\".WeldStartService is missing [jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".jndiDependencyService]",

              "jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".batch.artifact.factory is missing [jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".beanmanager]",

              "jboss.deployment.unit.\"FitnesEAR.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".deploymentCompleteService]"

          ]

      }

      11:44:07,086 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "sqljdbc4.jar" (runtime-name : "sqljdbc4.jar")

      11:44:07,103 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "FitnesEAR.ear" (runtime-name : "FitnesEAR.ear")

      11:44:07,106 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

      WFLYCTL0184:    New missing/unsatisfied dependencies:

            service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".beanmanager (missing) dependents: [service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".batch.artifact.factory, service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".weld.weldClassIntrospector]

            service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."FitnesEAR.ear".deploymentCompleteService]

            service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."FitnesEAR.ear".WeldStartService]

      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."FitnesEAR.ear"."Fitnes.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "Fitnes.war" of deployment "FitnesEAR.ear"

       

       

      11:44:07,186 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server

      11:44:07,193 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

      11:44:07,194 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

      11:44:07,194 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) started (with errors) in 8716ms - Started 575 of 820 services (19 services failed or missing dependencies, 374 services are lazy, passive or on-demand)

       

      I really need help!

        • 1. Re: Errors when running project on Wildfly
          Greg Jewell Apprentice

          randomguy13  wrote:

           

          11:44:07,070 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "FitnesEAR.ear")]) - failure description: {

              "WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"FitnesEAR.ear\".\"Fitnes.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of subdeployment \"Fitnes.war\" of deployment \"FitnesEAR.ear\"

              Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0041: Component class si.um.jpa3.ejb.ClaniBean for component ClaniBean has errors:

          WFLYJPA0033: Can't find a persistence unit named null in subdeployment \"Fitnes.war\" of deployment \"FitnesEAR.ear\""},

           

          It looks like wildfly is having difficulty finding your persistence.xml file.  It needs to be someplace that the war has visibility into.  If the file is currently in the ear's META-INF directory, you will need to move it into the EJB jar's META-INF directory.

           

          I also see this:

           

          randomguy13  wrote:

           

          11:44:07,086 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "sqljdbc4.jar" (runtime-name : "sqljdbc4.jar")

           

          JDBC drivers should really be installed as a JBoss module.  The reason for this is that data sources are defined within the standalone.xml (assuming standalone configuration).  The data source points to a JDBC driver configuration, and the JDBC driver configuration points to a specific class.  If that class isn't available through a module, things won't work properly.

           

          DataSource configuration - WildFly 10 - Project Documentation Editor

          1 of 1 people found this helpful
          • 2. Re: Errors when running project on Wildfly
            Teo Kac Newbie

            I fixed the first part. Now the only error is this:

             

             

            18:50:30,807 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "FitnesEAR.ear")]) - failure description: {

                "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.datasources.MySQL_home"],

                "WFLYCTL0180: Services with missing/unavailable dependencies" => [

                    "jboss.persistenceunit.\"FitnesEAR.ear/FitnesEJB.jar#Fitnes\" is missing [jboss.naming.context.java.jboss.datasources.MySQL_home]",

                    "jboss.persistenceunit.\"FitnesEAR.ear/FitnesEJB.jar#Fitnes\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jboss.datasources.MySQL_home]"

                ]

            }

            18:50:30,838 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "FitnesEAR.ear" (runtime-name : "FitnesEAR.ear")

            18:50:30,838 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

            WFLYCTL0184:    New missing/unsatisfied dependencies:

                  service jboss.naming.context.java.jboss.datasources.MySQL_home (missing) dependents: [service jboss.persistenceunit."FitnesEAR.ear/FitnesEJB.jar#Fitnes", service jboss.persistenceunit."FitnesEAR.ear/FitnesEJB.jar#Fitnes".__FIRST_PHASE__]

             

             

            My persistence.xml uses <jta-data-source>java:jboss/datasources/MySQL_home</jta-data-source> but I'm not sure if I have a sql.

            • 3. Re: Errors when running project on Wildfly
              Greg Jewell Apprentice

              randomguy13  wrote:

               

              WFLYCTL0184:    New missing/unsatisfied dependencies:

                    service jboss.naming.context.java.jboss.datasources.MySQL_home (missing) dependents: [service jboss.persistenceunit."FitnesEAR.ear/FitnesEJB.jar#Fitnes", service jboss.persistenceunit."FitnesEAR.ear/FitnesEJB.jar#Fitnes".__FIRST_PHASE__]

               

               

              My persistence.xml uses <jta-data-source>java:jboss/datasources/MySQL_home</jta-data-source> but I'm not sure if I have a sql.

              As you said, your persistence.xml references the MySQL_home datasource.  You need to configure this datasource in your standalone.xml.  This configuration will reference a JDBC driver, and the JDBC driver should be loaded into wildfly as a module.  I quoted a piece of your original post that showed "sqljdbc4.jar" as being successfully deployed.  I am guessing that you'll want to reference that JDBC driver in your datasource, but you'll need to move that jar out of the deployments directory and then create a module for it.

               

              Here's another link showing an example of creating a module for a driver:

               

              https://wiki.snowflakesoftware.com/display/GPWDOC/Install+JDBC+drivers+for+WildFly+10

               

              There are several examples in there, including one for SQL Server, which is what the sqljdbc4.jar connects to.

               

              Edit:  I wasn't paying close enough attention before.  Your datasource name is "MySQL_home", which implies that you are connecting to a MySQL DB instance.  However, the JDBC driver jar that was deployed is for SQL Server.  There is nothing that enforces what the name of a datasource should be.  It's possible that in the past that your software connected to a MySQL instance, and then changed at some point to use SQL Server, but the datasource name was never changed.  That's perfectly fine, if somewhat confusing.  Regardless, you should check to see what DB you are actually connecting to, and then configure the appropriate driver for that DB.

              1 of 1 people found this helpful