11 Replies Latest reply on Aug 30, 2013 9:05 AM by danos metal

    daytrade_deployment-error

    danos metal Newbie

      Hello to all,

       

      I am trying to deploy daytrade.

      The produced .ear file that i am pussing into jboss puts out the following log-error:

       

      =========================================================================

       

       

        JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /root/jboss-eap-6.1

       

       

        JAVA: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java

       

       

        JAVA_OPTS:  -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

       

       

      =========================================================================

       

       

      10:56:34,786 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1

      10:56:35,273 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA

      10:56:35,497 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) starting

      10:56:38,850 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA

      10:56:38,877 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA

      10:56:38,881 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

      10:56:38,945 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.14.GA

      10:56:39,193 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) JBAS010280: Activating Infinispan subsystem.

      10:56:39,561 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 36) JBAS011800: Activating Naming Subsystem

      10:56:39,600 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 41) JBAS013171: Activating Security Subsystem

      10:56:39,657 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 34) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

      10:56:40,041 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.15.Final)

      10:56:40,079 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

      10:56:40,134 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.15.Final

      10:56:40,615 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 24) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      10:56:40,707 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

      10:56:41,660 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080

      10:56:42,145 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080

      10:56:42,817 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /root/jboss-eap-6.1/standalone/deployments

      10:56:42,875 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "daytrader-ear-2.2.1.ear" (runtime-name: "daytrader-ear-2.2.1.ear")

      10:56:42,975 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999

      10:56:42,976 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447

      10:56:43,214 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      10:56:43,914 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "wsappclient.jar")

      10:56:43,916 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "dt-ejb.jar")

      10:56:43,918 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "web.war")

      10:56:43,944 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry entities.jar in /content/daytrader-ear-2.2.1.ear/wsappclient.jar  does not point to a valid jar for a Class-Path reference.

      10:56:44,009 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry soap.jar in /content/daytrader-ear-2.2.1.ear/wsappclient.jar  does not point to a valid jar for a Class-Path reference.

      10:56:44,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry entities.jar in /content/daytrader-ear-2.2.1.ear/web.war  does not point to a valid jar for a Class-Path reference.

      10:56:44,014 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry soap.jar in /content/daytrader-ear-2.2.1.ear/web.war  does not point to a valid jar for a Class-Path reference.

      10:56:44,016 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry streamer.jar in /content/daytrader-ear-2.2.1.ear/web.war  does not point to a valid jar for a Class-Path reference.

      10:56:44,200 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for daytrader

      10:56:45,123 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014211: No jndi bindings will be created for EJB tranTradeJPADirect since no views are exposed

      10:56:45,216 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named DirectSLSBBean in deployment unit subdeployment "dt-ejb.jar" of deployment "daytrader-ear-2.2.1.ear" are as follows:

       

       

              java:global/daytrader-ear-2.2.1/dt-ejb/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBRemote

              java:app/dt-ejb/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBRemote

              java:module/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBRemote

              java:jboss/exported/daytrader-ear-2.2.1/dt-ejb/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBRemote

              java:global/daytrader-ear-2.2.1/dt-ejb/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBLocal

              java:app/dt-ejb/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBLocal

              java:module/DirectSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.DirectSLSBLocal

       

       

      10:56:45,218 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named TradeSLSBBean in deployment unit subdeployment "dt-ejb.jar" of deployment "daytrader-ear-2.2.1.ear" are as follows:

       

       

              java:global/daytrader-ear-2.2.1/dt-ejb/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBRemote

              java:app/dt-ejb/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBRemote

              java:module/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBRemote

              java:jboss/exported/daytrader-ear-2.2.1/dt-ejb/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBRemote

              java:global/daytrader-ear-2.2.1/dt-ejb/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBLocal

              java:app/dt-ejb/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBLocal

              java:module/TradeSLSBBean!org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBLocal

       

       

      10:56:47,259 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 25) JBAS018559: Deployed "daytrader-ear-2.2.1.ear" (runtime-name : "daytrader-ear-2.2.1.ear")

      10:56:47,290 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.naming.context.java.ConnectionFactory (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."web.war".component."org.apache.geronimo.samples.daytrader.web.prims.ejb3.PingServlet2MDBQueue".START]

            service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env.jms.QueueConnectionFactory (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.TradeSLSBBean.START]

            service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env.jms.TopicConnectionFactory (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.TradeSLSBBean.START]

            service jboss.naming.context.java.jboss.java:jdbc.TradeDataSource (missing) dependents: [service jboss.persistenceunit."daytrader-ear-2.2.1.ear/dt-ejb.jar#daytrader", service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jdbc.TradeDataSource]

            service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.ConnectionFactory (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.QueueConnectionFactory, service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TopicConnectionFactory]

            service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.TradeBrokerQueue (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TradeBrokerQueue]

            service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.TradeStreamerTopic (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TradeStreamerTopic]

            service jboss.ra.hornetq-ra (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.DTStreamer3MDB.CREATE, service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.DTBroker3MDB.CREATE]

       

       

      10:56:47,354 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

      10:56:47,355 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      10:56:47,357 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) started (with errors) in 14003ms - Started 313 of 451 services (70 services failed or missing dependencies, 67 services are passive or on-demand)

       

      Can you please provide me some help on how to resolve it??

       

      Danos

        • 1. Re: daytrade_deployment-error
          ehugonnet Apprentice

          You have to declare your jms-connection-factories and jms-destinations according to what is specified in your ear.

          Look into Circular dependency error while deploying ear the standalone-full.xml seems to be ok.

           

           

          For the datasource configuration you can also configure it in the standalone.xml following the documentation : DataSource configuration - JBoss AS 7.2 - Project Documentation Editor

          • 2. Re: Re: daytrade_deployment-error
            danos metal Newbie

            Thank for your reply Emmanuel,

             

            What i have done so far for the JBoss is the following

             

            1) Added a module.xml and the mysql-connector-java-5.0.8-bin.jar at the path /jboss-eap-6.1/modules/system/layers/base/mysql/main/

             

            2)Second change the standalone.xml as i have attached it.To be more specific I did add the following lines at the datasource as

             

            <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>

                            <drivers>

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

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

                                </driver>

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

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

                                </driver>

                            </drivers>

                    </datasources>

             

            I should also modify the standalone-full.xml as the one you gave me??

             

            Now about the daytrade application,

             

            Should i modify the jboss-web.xml??

            Are there any other files that i should modify ??

             

            I have attached the jboss-web.xml

            • 3. Re: Re: daytrade_deployment-error
              ehugonnet Apprentice

              Your jboss-web.xml has a trailing  </message-destination-ref> on ligne 46.

              I'm not sure about daytrader-jboss5-destinations-service.xml and hornetq-jms.xml support in EAP 6.

              • 4. Re: Re: Re: daytrade_deployment-error
                danos metal Newbie

                ok i did change my jboss-web.xml looking like this

                 

                <?xml version="1.0" encoding="UTF-8"?>
                
                
                <!--
                    Licensed to the Apache Software Foundation (ASF) under one or more
                    contributor license agreements.  See the NOTICE file distributed with
                    this work for additional information regarding copyright ownership.
                    The ASF licenses this file to You under the Apache License, Version 2.0
                    (the "License"); you may not use this file except in compliance with
                    the License.  You may obtain a copy of the License at
                
                
                       http://www.apache.org/licenses/LICENSE-2.0
                
                
                    Unless required by applicable law or agreed to in writing, software
                    distributed under the License is distributed on an "AS IS" BASIS,
                    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
                    See the License for the specific language governing permissions and
                    limitations under the License.
                -->
                
                
                <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd">
                
                
                <jboss-web>
                
                
                      <resource-ref>
                         <res-ref-name>java:jboss/jdbc/TradeDataSource</res-ref-name>
                         <!-- If using DB2, comment out this line -->
                         <!--<jndi-name>jdbc/TradeDataSource</jndi-name>-->
                         <!-- If using MySql or Oracle, use this line -->
                         <jndi-name>java:jboss/jdbc/TradeDataSource</jndi-name>
                      </resource-ref>
                
                
                      <resource-ref>
                         <res-ref-name>jms/QueueConnectionFactory</res-ref-name>
                         <jndi-name>java:jboss/ConnectionFactory</jndi-name>
                      </resource-ref>
                
                
                      <resource-ref>
                         <res-ref-name>jms/TopicConnectionFactory</res-ref-name>
                         <jndi-name>java:jboss/ConnectionFactory</jndi-name>
                      </resource-ref>
                
                
                      <message-destination-ref>
                         <message-destination-ref-name>jms/TradeBrokerQueue</message-destination-ref-name>
                         <jndi-name>java:jboss/jms/TradeBrokerQueue</jndi-name>
                      </message-destination-ref>
                
                
                      <message-destination-ref>
                         <message-destination-ref-name>jms/TradeStreamerTopic</message-destination-ref-name>
                         <jndi-name>java:jboss/jms/TradeStreamerTopic</jndi-name>
                      </message-destination-ref>
                
                
                </jboss-web>
                
                

                 

                 

                i think something is wrong with this configuration as i still have a lot of missing dependencies...

                JBAS014775:    New missing/unsatisfied dependencies:

                      service jboss.jdbc-driver.mysql (missing) dependents: [service jboss.driver-demander.java:jboss/jdbc/TradeDataSource, service jboss.data-source.java:jboss/jdbc/MySqlDS, service jboss.driver-demander.java:jboss/jdbc/MySqlDS, service jboss.data-source.java:jboss/jdbc/TradeDataSource]

                      service jboss.naming.context.java.ConnectionFactory (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.QueueConnectionFactory, service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TopicConnectionFactory, service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."web.war".component."org.apache.geronimo.samples.daytrader.web.prims.ejb3.PingServlet2MDBQueue".START]

                      service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env.jms.QueueConnectionFactory (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.TradeSLSBBean.START]

                      service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env.jms.TopicConnectionFactory (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.TradeSLSBBean.START]

                      service jboss.naming.context.java.jboss.java:jdbc.TradeDataSource (missing) dependents: [service jboss.persistenceunit."daytrader-ear-2.2.1.ear/dt-ejb.jar#daytrader"]

                      service jboss.naming.context.java.jms.TradeBrokerQueue (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TradeBrokerQueue]

                      service jboss.naming.context.java.jms.TradeStreamerTopic (missing) dependents: [service jboss.naming.context.java.module."daytrader-ear-2.2.1".web.env.jms.TradeStreamerTopic]

                      service jboss.ra.hornetq-ra (missing) dependents: [service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.DTStreamer3MDB.CREATE, service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."dt-ejb.jar".component.DTBroker3MDB.CREATE]

                 

                 

                thanks,

                danos

                • 5. Re: Re: Re: daytrade_deployment-error
                  Tomaz Cerar Master

                  You are missing definition for datasource named: TradeDataSource

                   

                  and you are missing whole messaging subsystem that provides JMS queues.

                   

                  i would recommending you to start with original standalone.xml and add configuration for datasources and all your jms queues that your jboss-web.xml refers to.

                   

                   

                   

                  --

                  tomaz

                  • 6. Re: Re: Re: Re: daytrade_deployment-error
                    danos metal Newbie

                    Ok so let's take see it from two views first the view of daytrade,

                    i have three basic files there right?

                    -->jboss-web.xml (definitions of datasources right??)

                    -->/config/daytrader-jboss5-destinations-service.xml (i do not use jboss5 as i am on jboss-eap-6.1 does it matter??)

                    -->./config/hornetq-jms.xml (jms file right?)

                     

                    All of the above files are attached.

                     

                    then the view of JBoss,

                    i assume there the basic config file to play with is the standalone.xml.I have also include the mysql.jar connector at the modules if that works for it.

                    Just to remind you i am using jboss-eap-6.1 ,stable version.

                     

                    Your help is valuable to me,

                    thanks

                    • 7. Re: Re: Re: Re: daytrade_deployment-error
                      Justin Bertram Master

                      -->/config/daytrader-jboss5-destinations-service.xml (i do not use jboss5 as i am on jboss-eap-6.1 does it matter??)

                      Yes, this matters.  This file is not relevant to EAP 6.1.  It defines legacy MBeans used by JBoss Messaging (used in JBoss AS 5.x).

                       

                      -->./config/hornetq-jms.xml (jms file right?)

                      This particular file is also not relevant for EAP 6.1.  It would be used for HornetQ as configured in JBoss AS 5.x or 6.x.

                       

                      You can use *-jms.xml files in EAP 6.1, but the format is different.  See Messaging configuration - WildFly 8 for an example (scroll down to the "Deployment of -jms.xml files" section).  To be clear, you can only define JMS queues and topics.  You can't defined connection factories.

                      • 8. Re: daytrade_deployment-error
                        danos metal Newbie

                        So that leaves me only the jboss-web.xml and a daytrade-jms.xml ??

                        • 9. Re: daytrade_deployment-error
                          Justin Bertram Master

                          I have no idea what that leaves you with.  I'm just saying that the two files I mentioned are not relevant for EAP 6.1.

                          • 10. Re: Re: daytrade_deployment-error
                            danos metal Newbie

                            i am uploading some files to check

                            • 11. Re: Re: Re: daytrade_deployment-error
                              danos metal Newbie

                              Using the the standalone-full.xml and making some changes to the files i managed to minimize the faults to the above

                               

                              11:39:58,432 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "daytrader-ear-2.2.1.ear" (runtime-name : "daytrader-ear-2.2.1.ear")

                              11:39:58,466 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

                              JBAS014775:    New missing/unsatisfied dependencies:

                                    service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."web.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."daytrader-ear-2.2.1.ear".deploymentCompleteService]

                                    service jboss.jdbc-driver.mysql (missing) dependents: [service jboss.data-source.java:jboss/TradeDataSource, service jboss.driver-demander.java:jboss/TradeDataSource]

                                    service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env.jms.ConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env."org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBBean".queueConnectionFactory, service jboss.naming.context.java.comp."daytrader-ear-2.2.1".dt-ejb.TradeSLSBBean.env."org.apache.geronimo.samples.daytrader.ejb3.TradeSLSBBean".topicConnectionFactory]

                                    service jboss.naming.context.java.jboss.jdbc.TradeDataSource (missing) dependents: [service jboss.persistenceunit."daytrader-ear-2.2.1.ear/dt-ejb.jar#daytrader"]

                              JBAS014777:   Services which failed to start:      service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."web.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."daytrader-ear-2.2.1.ear"."web.war".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "web.war" of deployment "daytrader-ear-2.2.1.ear"

                               

                              The thing i can not understand why i am having missing dependencies for the datasource as i defined it in both jboss-web.xml,jboss.xml and in standalone-full.xml.

                              As for the ConnectionFactory i had defined these in standalone-full.xml as below:

                               

                                 <connection-factory name="QueueConnectionFactory">

                                                        <connectors>

                                                              <connector-ref connector-name="in-vm" />

                                                        </connectors>

                                                        <entries>

                                                                      <entry name="QueueConnectionFactory"/>

                                                        </entries>

                                                    </connection-factory>

                                                    <connection-factory name="TopicConnectionFactory">

                                                        <connectors>

                                                              <connector-ref connector-name="in-vm" />

                                                        </connectors>

                                                        <entries>

                                                                      <entry name="TopicConnectionFactory"/>

                                                        </entries>

                                                    </connection-factory>

                               

                              About the jndi names of datasource are the same in jboss-web.xml and jboss.xml and at the standalone-full.xml, so why am i getting the error of datasource??
                              I have attached the appropriate files.
                              Can you explain me what are the erros that i get?What i need to do further?

                               

                              Danos