2 Replies Latest reply: Jan 27, 2013 5:18 AM by Justin James RSS

    EAR Deployment issue

    Justin James
      Hello -

      I'm getting the following error while performing deployment on cloud.
      Also the same EAR is successfully deployed into my workstation which is running Weblogic12c.
      I'm wondering may be this is bug while seeing these line from the Deployment Error log.

      Line 1 : Error parsing descriptor in Web appplication "****"
      Line 2 : http:/***:<null>* is coming in the error.

      in line1 found 3p in application.(not a big thing).

      Please have a look at Java Cloud Service Job logs and web.xml files.

      Thanks in advance,
      Justin.

      1. Deployment Error log.
      2013-01-16 06:21:37 CST: Starting action "Deploy Application"
      2013-01-16 06:21:37 CST: Deploy Application started
      2013-01-16 06:21:39 CST: weblogic.application.ModuleException: [HTTP:101064][WebAppModule(HelloCloud:HelloCloudService)] 
      Error parsing descriptor in Web appplication "****"
      weblogic.application.ModuleException: VALIDATION PROBLEMS WERE FOUND
        problem: cvc-enumeration-valid: string value '3.0' is not a valid enumeration value for web-app-versionType in namespace http:/****:<null>
           at weblogic.servlet.internal.WebAppModule.loadDescriptor(Unknown Source)
           at weblogic.servlet.internal.WebAppModule.prepare(Unknown Source)
           at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
           at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
           at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
           at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
           at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
           at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
           at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
           at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
           at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
           at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
           at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
           at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
           at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
           at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
           at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
           at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
           at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
           at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
           at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
           at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
           at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
           at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
           at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
      Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
        problem: cvc-enumeration-valid: string value '3.0' is not a valid enumeration value for web-app-versionType in namespace http:/****:<null>
           at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
           at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
           at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
           at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(Unknown Source)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(Unknown Source)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(Unknown Source)
           at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(Unknown Source)
           at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
           ... 27 more
      
      weblogic.application.ModuleException: VALIDATION PROBLEMS WERE FOUND
        problem: cvc-enumeration-valid: string value '3.0' is not a valid enumeration value for web-app-versionType in namespace http:/****:<null>
      2013-01-16 06:21:39 CST: WLS action state: failed
      2013-01-16 06:21:39 CST: Action FAILED with WLS state: failed
      2013-01-16 06:21:39 CST: Application deployment failed.
      2013-01-16 06:21:39 CST: "Deploy Application" complete: status FAILED
      2. My Web.xml file
      <?xml version="1.0" encoding="UTF-8"?>
      <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" id="WebApp_ID" version="3.0">
        <display-name>HelloCloudService</display-name>
        <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
        </welcome-file-list>
      </web-app>
      3. whitelist.log
      WARNING : There are 3 warnings(s) found for c:\HelloCloudEAR.ear.
       WARNING : Path:c:\HelloCloudEAR.ear (3 Warnings)
        WARNING : Path:c:\HelloCloudEAR.ear (3 Warnings)
         WARNING : Path:HelloCloudService.war (3 Warnings)
          WARNING : Path:WEB-INF/web.xml (1 Warning)
           WARNING : 1:Recommended child element "login-config" missing under element /javaee:web-app.
           WARNING : If you want to make your application public, you can have empty <login-config/> in your web.xml. If you need authentication then you must have <login-config> and its child <auth-method> element in web.xml. Without this element(<login-config>), users may be challenged by SSO, but the application code will be executed as anonymous user only. Line No:2.
          WARNING : Path:WEB-INF/weblogic.xml (2 Warnings)
           WARNING : 1:Recommended child element "jsp-descriptor" missing under element /orcl-weblogic:weblogic-web-app.
           WARNING : 
           WARNING : If you have a JSP file that is not pre-compiled, The compilation errors could be shown on the browser. It is recommended to include <jsp-descriptor><verbose>false</verbose></jsp-descriptor> in weblogic.xml.
           WARNING : Line No:2.
           WARNING : 2:Recommended child element "session-descriptor" missing under element /orcl-weblogic:weblogic-web-app.
           WARNING : 
           WARNING : You will be required to have distinct cookie-path, if multiple applications are accessed with in the same SSO session or if you have multiple applications with different auth-method(CLIENT-CERT, FORM, BASIC) in the same service instance.
           WARNING : Line No:2.
       WARNING : c:\HelloCloudEAR.ear had  3 warning(s).
          INFO : Whitelist validation has completed with 0 error(s) and 3 warning(s).
        • 1. Re: EAR Deployment issue
          Nilesh
          Justin ,
          Java Cloud Service currently does not support Servlet 3.0 Spec (Part of Java EE6) , Weblogic 12 supports Servlet 3.0.
          This is issue is caused by the incompatibility.
          • 2. Re: EAR Deployment issue
            Justin James
            Thank you Nilesh for your response.

            From the following link, I know that JEE6 is supported by cloud.

            http://docs.oracle.com/cloud/CSJSU/dev_app.htm#BCEDAHCE

            Can you pleas share, what are the other Java EE release 6 components which is not supported by cloud.

            TL;DR : As everyone knows...in Weblogic12c - c stands for cloud.
            And now Cloud is not supporting 12c. :p

            Thanks,
            Justin.