8 Replies Latest reply on Sep 19, 2014 3:37 PM by Zaheer Boovaji

    Error When Starting Jboss-as-7.1.0

    Zaheer Boovaji Newbie

      Hello,.. When I Deploy my EJB Project and make necessary adjustments in standalone.xml and create module.xml file and start the server it is showing an Error saying

       

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.naming.context.java.CrudDS (missing) dependents: [service jboss.persistenceunit."CrudEJB.jar#CrudPU"]

       

      05:00:27,179 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDSMissing[jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDS]"]}}}

       

       

      If I Show u the Whole Console when i run the server please refer below and please help me to fix this:

       

      05:00:23,174 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      05:00:23,464 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      05:00:23,537 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting

      05:00:24,761 INFO  [org.xnio] XNIO Version 3.0.3.GA

      05:00:24,761 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      05:00:24,774 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

      05:00:24,784 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.2.GA

      05:00:24,819 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      05:00:24,825 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      05:00:24,901 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      05:00:24,912 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      05:00:24,922 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

      05:00:24,934 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

      05:00:24,938 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.6.final

      05:00:25,029 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      05:00:25,145 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

      05:00:25,437 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      05:00:25,477 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

      05:00:25,478 INFO  [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)

      05:00:25,696 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.1.GA

      05:00:25,841 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory F:\STUDENT DVD2\JBOSS APPLICATION SERVER\New JBOSS 7.1.0\jboss-as-7.1.0.Final\jboss-as-7.1.0.Final\standalone\deployments

      05:00:25,844 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment CrudEJB.jar

      05:00:25,854 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found CrudEJB.jar in deployment directory. To trigger deployment create a file called CrudEJB.jar.dodeploy

      05:00:25,946 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

      05:00:25,954 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447

      05:00:25,971 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999

      05:00:26,148 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      05:00:26,364 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.jdbc-driver.com_mysql (missing) dependents: [service jboss.data-source.java:jboss/datasources/CrudDS]

       

       

      05:00:26,398 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "CrudEJB.jar"

      05:00:26,500 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for CrudPU

      05:00:26,568 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UserDAO in deployment unit deployment "CrudEJB.jar" are as follows:

       

       

        java:global/CrudEJB/UserDAO!com.dao.UserDAO

        java:app/CrudEJB/UserDAO!com.dao.UserDAO

        java:module/UserDAO!com.dao.UserDAO

        java:global/CrudEJB/UserDAO

        java:app/CrudEJB/UserDAO

        java:module/UserDAO

       

       

      05:00:26,573 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named DogDAO in deployment unit deployment "CrudEJB.jar" are as follows:

       

       

        java:global/CrudEJB/DogDAO!com.dao.DogDAO

        java:app/CrudEJB/DogDAO!com.dao.DogDAO

        java:module/DogDAO!com.dao.DogDAO

        java:global/CrudEJB/DogDAO

        java:app/CrudEJB/DogDAO

        java:module/DogDAO

       

       

      05:00:26,577 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named DogFacadeImp in deployment unit deployment "CrudEJB.jar" are as follows:

       

       

        java:global/CrudEJB/DogFacadeImp!com.facade.DogFacade

        java:app/CrudEJB/DogFacadeImp!com.facade.DogFacade

        java:module/DogFacadeImp!com.facade.DogFacade

        java:global/CrudEJB/DogFacadeImp

        java:app/CrudEJB/DogFacadeImp

        java:module/DogFacadeImp

       

       

      05:00:26,580 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UserFacadeImp in deployment unit deployment "CrudEJB.jar" are as follows:

       

       

        java:global/CrudEJB/UserFacadeImp!com.facade.UserFacade

        java:app/CrudEJB/UserFacadeImp!com.facade.UserFacade

        java:module/UserFacadeImp!com.facade.UserFacade

        java:global/CrudEJB/UserFacadeImp

        java:app/CrudEJB/UserFacadeImp

        java:module/UserFacadeImp

       

       

      05:00:26,937 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 4133ms - Started 227 of 311 services (10 services failed or missing dependencies, 72 services are passive or on-demand)

      05:00:27,143 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "CrudEJB.jar" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDSMissing[jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDS]"]}

      05:00:27,176 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment CrudEJB.jar in 31ms

      05:00:27,177 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.naming.context.java.CrudDS (missing) dependents: [service jboss.persistenceunit."CrudEJB.jar#CrudPU"]

       

       

      05:00:27,179 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDSMissing[jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDS]"]}}}

        • 1. Re: Error When Starting Jboss-as-7.1.0
          jaikiran pai Master

          I haven't looked at the error message in detail, but with WildFly (JBoss AS has been renamed to WildFly) 8.1.0.Final released for a while now, I don't think it's a good idea to be using JBoss AS 7.1.0. Can you try it against WildFly 8.1.0.Final from here Downloads · WildFly and see how it goes there?

          • 2. Re: Error When Starting Jboss-as-7.1.0
            Frank Langelage Master

            service jboss.jdbc-driver.com_mysql (missing) dependents: [service jboss.data-source.java:jboss/datasources/CrudDS]

             

            Your database configuration is not correct.

            Did you add mysql driver as module or as deployment or not at all?

            Seems you configured a CrudDS which needs it.

            • 3. Re: Error When Starting Jboss-as-7.1.0
              Zaheer Boovaji Newbie

              Yeah, I have added mysql driver in jboss-as-7.1.0.Final/modules/com/mysql/main/module.xml

               

              And inside the module.xml the code is:

               

              <?xml version='1.0' encoding='UTF-8'?>

              <!--

                ~ JBoss copyrights

                ~ http://community.jboss.org/wiki/DataSourceConfigurationInAS7

              -->

              <module xmlns="urn:jboss:module:1.0" name="com.mysql">

                <resources>

                  <resource-root path="mysql-connector-java-5.1.19-bin"/>

                </resources>

                <dependencies>

                  <module name="javax.api"/>

                  <module name="javax.transaction.api"/>

                </dependencies>

              </module>

               

              And Below is my the datasource i have configured in  standalone.xml file

               

              <datasources>

                              <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">

                                  <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>

                                  <driver>h2</driver>

                                  <security>

                                      <user-name>sa</user-name>

                                      <password>sa</password>

                                  </security>

                              </datasource>

                <datasource jndi-name="java:jboss/datasources/CrudDS" pool-name="CrudDS" enabled="true" use-java-context="true">

                                  <connection-url>jdbc:mysql://localhost:3306/CrudDB</connection-url>

                                  <driver>com.mysql</driver>

                                  <security>

                                      <user-name>root</user-name>

                                      <password></password>

                                  </security>

                              </datasource>

                              <drivers>

                                  <driver name="h2" module="com.h2database.h2">

                                      <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>

                                  </driver>

                                  <driver name="com.mysql" module="com.mysql">

                                      <xa-datasource-class>com.mysql.jdbc.Driver</xa-datasource-class>

                                  </driver>

                              </drivers>

                          </datasources>

               

              can't figure out where the problem is

              • 4. Re: Error When Starting Jboss-as-7.1.0
                Kuldeep Sharma Novice

                Add your Jar file to jboss-as-7.1.0.Final/modules/com/mysql/main/ .

                And make changes to your resource path in module.xml file.


                <resource-root path="mysql-connector-java-5.1.19-bin.jar(Full Name with Extension)"/>

                 

                Then check if it works.

                 

                1 of 1 people found this helpful
                • 5. Re: Error When Starting Jboss-as-7.1.0
                  Mitesh Manani Newbie

                  problem lies in the below block.. you need to give proper jar file name.

                   

                  <module xmlns="urn:jboss:module:1.0" name="com.mysql">

                    <resources>

                      <resource-root path="mysql-connector-java-5.1.19-bin"/>

                    </resources>

                  1 of 1 people found this helpful
                  • 6. Re: Error When Starting Jboss-as-7.1.0
                    Zaheer Boovaji Newbie

                    Yeah, I have put .jar as extension also i have added mysql-connector-java-5.1.19-bin.jar file in jboss-as-7.1.0.Final/modules/com/mysql/main/ folder but too same problem exists

                     

                    dont know what it is saying about CrudDS which is my datasource

                     

                    19:42:54,561 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "CrudEJB.jar" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDSMissing[jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDS]"]}

                    19:42:54,586 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment CrudEJB.jar in 23ms

                    19:42:54,587 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

                    JBAS014775:    New missing/unsatisfied dependencies:

                          service jboss.naming.context.java.CrudDS (missing) dependents: [service jboss.persistenceunit."CrudEJB.jar#CrudPU"]

                     

                     

                    19:42:54,589 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDSMissing[jboss.persistenceunit.\"CrudEJB.jar#CrudPU\"jboss.naming.context.java.CrudDS]"]}}}

                    • 7. Re: Error When Starting Jboss-as-7.1.0
                      Frank Langelage Master

                      Show us your persistence.xml. What's your setting for jta-data-source?

                      Seems it's only java:CrudDS and not java:jboss/datasources/CrudDS.

                      • 8. Re: Error When Starting Jboss-as-7.1.0
                        Zaheer Boovaji Newbie

                        Thanks, Frank Langelage also all the Others who have engaged in the Discussion

                        Actually the Problem was in persistence.xml

                        I have written it as java:/CrudDS but as Frank Said it Should be java:jboss/datasources/CrudDS