5 Replies Latest reply on May 31, 2016 5:00 AM by masster

    Migrating EAR from AS 7.0.2 to AS 7.1.0

    masster Newbie

      Hi guys,

       

      did anyone encounter any problem with EAR deployment on AS 7.1.0 that worked on 7.0.2?

       

      I have EAR with this structure :

       

      appEAR

      • lib
        • aspect.jar
        • appEjbClient.jar
        • appResource.jar
        • ojdbc6.jar
      • META-INF
      • app.war
      • appEJB.jar

       

      I've created datasources that I need on both servers.

      After I deploy it on 7.0.2, everything works fine but when I try to deploy it on 7.1.0 I get this problem:

       

      Failed to enable appEAR.ear.

       

       

      Unexpected HTTP response: 500

       

       

      Request

      {

          "address" => [("deployment" => "appEAR.ear")],

          "operation" => "deploy"

      }

       

       

      Response

       

       

      Internal Server Error

      {

          "outcome" => "failed",

          "failure-description" => {

              "JBAS014671: Fehlgeschlagene Dienste" => {"jboss.deployment.subunit.\"appEAR.ear\".\"appEJB.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"appEAR.ear\".\"appEJB.jar\".INSTALL: JBAS018733: Verarbeitung von Phase INSTALL von subdeployment \"appEJB.jar\" of deployment \"appEAR.ear\" fehlgeschlagen

          Caused by: java.lang.RuntimeException: javax.ejb.EJBException: javax.naming.NameNotFoundException: Error looking up appEAR/appEJB/AppEao!com.app.eao.AppEao, service service jboss.naming.context.java.global.appEAR.appEJB.\"AppEao!com.app.eao.AppEao\" is not started

          Caused by: javax.ejb.EJBException: javax.naming.NameNotFoundException: Error looking up appEAR/appEJB/AppEao!com.app.eao.AppEao, service service jboss.naming.context.java.global.appEAR.appEJB.\"AppEao!com.app.eao.AppEao\" is not started

          Caused by: javax.naming.NameNotFoundException: Error looking up appEAR/appEJB/AppEao!com.app.eao.AppEao, service service jboss.naming.context.java.global.appEAR.appEJB.\"AppEao!com.app.eao.AppEao\" is not started"},

              "JBAS014771: Dienste mit fehlenden/unverfügbaren Abhängigkeiten " => [

                  "jboss.deployment.unit.\"appEAR.ear\".deploymentCompleteService [jboss.deployment.subunit.\"appEAR.ear\".\"appEJB.jar\".deploymentCompleteService] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.TransactionDataEao.ValidatorFactory [jboss.naming.context.java.comp.appEAR.appEJB.TransactionDataEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.AppBean.Validator [jboss.naming.context.java.comp.appEAR.appEJB.AppBean] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.MasterDataEao.Validator [jboss.naming.context.java.comp.appEAR.appEJB.MasterDataEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.LoggingAspect.ValidatorFactory [jboss.naming.context.java.comp.appEAR.appEJB.LoggingAspect] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.MasterDataEao.ValidatorFactory [jboss.naming.context.java.comp.appEAR.appEJB.MasterDataEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.AppBean.ValidatorFactory [jboss.naming.context.java.comp.appEAR.appEJB.AppBean] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.AppEao.Validator [jboss.naming.context.java.comp.appEAR.appEJB.AppEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.TransactionDataEao.Validator [jboss.naming.context.java.comp.appEAR.appEJB.TransactionDataEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.AppEao.ValidatorFactory [jboss.naming.context.java.comp.appEAR.appEJB.AppEao] fehlt",

                  "jboss.naming.context.java.comp.appEAR.appEJB.LoggingAspect.Validator [jboss.naming.context.java.comp.appEAR.appEJB.LoggingAspect] fehlt"

              ]

          },

          "rolled-back" => true

      }

       

      I'm sorry that part of the trace is in german but basically it says:

      Verarbeitung von Phase INSTALL von subdeployment - "Failed to process phase INSTALL of subdeployment"

      fehlt - "is missing"

       

      So, does anyone have a solution for this problem?

      Also just to mention, I encounter the same problem when I try to deploy the EAR on the EAP 6.4.