1 2 Previous Next 18 Replies Latest reply on May 15, 2015 3:51 AM by sganeshraj Go to original post
      • 15. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
        sganeshraj

        Hi ,

         

        while deploying my specj.ear i am hitting following error, can any one help me here?

        Unknown error

         

        Unexpected HTTP response: 500 Request { "address" => [("deployment" => "specj.ear")], "operation" => "deploy" } Response Internal Server Error { "outcome" => "failed", "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => [ "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.OrderAuditSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.ItemBrowserSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.LoaderMDB.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.ReceiveMDB.START Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".buyerQueueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.BuyerMDB.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.OrderSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.WorkOrderSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.RunConfigSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.LoaderSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.LargeOrderSenderSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.PurchaseOrderMDB.START Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".LargeOrderSenderSession.env.\"org.spec.jent.ejb.orders.session.LargeOrderSenderSession\".queueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.SupplierAuditSession.START Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".SupplierSession.env.\"org.spec.jent.ejb.supplier.session.SupplierSession\".queueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]", "jboss.web.deployment.default-host./specj Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".BuyerMDB.env.\"org.spec.jent.ejb.supplier.mdb.BuyerMDB\".queueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".jboss.security.jacc Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.LargerOrderMDB.START Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".LoaderSession.env.\"org.spec.jent.loader.session.LoaderSession\".queueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.MfgSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.FulfillOrderMDB.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.CustomerSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.SupplierSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".jndiDependencyService Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.MessageSenderSession.START Missing[JBAS014861: ]", "jboss.deployment.subunit.\"specj.ear\".\"specj.jar\".component.MfgAuditSession.START Missing[JBAS014861: ]", "jboss.naming.context.java.comp.specj.\"specj.jar\".MessageSenderSession.env.\"org.spec.jent.ejb.mfg.session.MessageSenderSession\".fulfillOrderQueueConnFactory Missing[jboss.naming.context.java.jboss.activemq.TopicConnectionFactoryt]" ]}, "rolled-back" => true }

         

         

        kindly let me know what should i do get this issue fixed

         

        i have followed WebService endpoint and WAR module causes DuplicateServiceException and Patrik Varga's Blog: JBoss AS7 JNDI and Migration from AS6 post where it is mentioned jndi-name tag will be culprit. I have those details entered into my ejb-jar.xml file. Still it fails with the same error.

         

        Also i have made following changes too... still no use...

        The solution is to change configuration file as7/standalone/configuration/standalone.xml (or whichever your using).

         

        From:
           <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>

         

        To:

           <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>

        • 16. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
          whitingjr

          Did you follow the instructions detailed in this forum post ? If you had then these errors would not appear.

           

          You do appear to have a lot of errors like ".queueConnFactory Missing". Which indicates you didn't add the resource references (resource-ref) for each MDB with the XA JMS Connection Factory. Look at the first page of this forum for examples.

          • 17. Re: SPECjEnterprise2010 new missing/unsatisfied dependencies.
            sganeshraj

            thanks for your reply Jeremy Whiting.

            I have included "resource-ref" in my ejb-jar.xml file.

            Note: I dont see ATTACH option to include files while replying to the post.

            I have attached my ejb-jar.xml and persistence.xml under following post.

            specjenterprise2010 - JBAS014861

            1 2 Previous Next