8 Replies Latest reply on Jul 22, 2013 5:41 PM by William Lovett

    Deploying as an Ear File using Manifests.  JBAS014862: Operation cancelled

    William Lovett Newbie

      Ladies and Gents,

       

      Using JBoss EAP 6.0, which I think is JBoss AS 7.x. 

       

      I've successfully deployed my ADF 10g project as a WAR through both JDeveloper and Eclipse.  Now it's time to deploy it as an EAR through Eclipse using JBoss Tools.  Much to my chagrin, this has proven more aggravating than I had hoped.  I've read multiple posts with no success and the error messages I do get back are especially cryptic.  Any help would be appreciated.

       

      Here's the EAR layout

       

      MyMulti.ear

      |

      |-- META-INF

           |-- application.xml

           |-- Manifest.MF

      |

      |-- MyMultiEJB.jar

      |

      |-- MyMultiWeb.jar

      |

      |-- All of my other dependent jars

       

       

      The manifest file under my .ear's META-INF simply says "Manifest-Version: 1.0"

       

      Here are the rest of the application and manifest files:

       

      Application xml

       

      <?xml version="1.0" encoding="UTF-8"?>
      <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" id="Application_ID" version="6">
        <display-name>MyMulti</display-name>
        <module>
          <web>
            <web-uri>MyMultiWeb.war</web-uri>
            <context-root>MyMultiWeb</context-root>
          </web>
        </module>
        <module>
          <ejb>MyMultiEJB.jar</ejb>
        </module>
      </application>
      

       

      The EJB's Manifest

       

      Manifest-Version: 1.0
      Class-Path: eclipselink.jar 
       org.eclipse.persistence.asm.jar 
       org.eclipse.persistence.core.jar 
       commons-collections.jar 
       commons-lang.jar
      
      

       

      The Web's Manifest

       

      Manifest-Version: 1.0
      Class-Path: MyMultiEJB.jar 
       adf-controller.jar 
       adf-faces-api.jar 
       adf-faces-impl.jar 
       adfbinding.jar 
       adfcm.jar 
       adfm.jar 
       adfmtl.jar 
       adfmweb.jar 
       adfshare.jar 
       adfui.jar 
       bc4jct.jar 
       bc4jctejb.jar 
       bc4jdomorcl.jar 
       bc4jimdomains.jar 
       bc4jmt.jar 
       bc4jmtejb.jar 
       collections.jar 
       commons-beanutils.jar 
       commons-collections.jar 
       commons-digester.jar 
       commons-lang.jar 
       commons-logging.jar 
       dms.jar 
       eclipselink.jar 
       iText-5.0.5.jar 
       jsf-api_1-1.jar 
       jsf-impl_1-1.jar 
       ojdbc14.jar 
       ojdbc14dms.jar 
       orai18n-mapping.jar 
       org.eclipse.persistence.asm.jar 
       org.eclipse.persistence.core.jar 
       poi.jar 
       runtime12.jar 
       translator.jar 
       xml.jar 
       xmlparserv2.jar
      
      

       

      In Eclipse, if I right-click on the top MyMulti project and select "Run As Server", the server will boot up and attempt to run the exploded ear file.  It then sits there forever with the exploded ear and two other files: MyMulti.ear.dodeploy and MyMulti.ear.isdeploying.  Nothing else ever happens.  No error messages.

       

      If I exit eclipse, start up JBoss manually, and then drag and drop my ear into the deployment folder, I receive the following ...

       

      ... server boots up fine
      10:30:38,975 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 48650ms - Started 181 of 248 services (65 services are passive or on-demand)
      10:31:34,098 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "MyMulti.ear" (runtime-name: "MyMulti.ear")
      10:41:34,105 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "MyMulti.ear" was rolled back with the following failure message: "JBAS014862: Operation cancelled"
      10:41:34,111 WARN  [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014626: Operation was interrupted before stability could be reached
      

       

      The file is 38 megs.  My WAR was the same size and while it took about 20 minutes to deploy, there weren't any problems.

       

      Any thoughts?

        • 1. Re: Deploying as an Ear File
          William Lovett Newbie

          I should note that I did not add any jboss-deployment-structure files or anything of that nature.  I simply used the web.xml, faces-config, and other initialization files from my war.

          • 2. Re: Deploying as an Ear File
            William Lovett Newbie

            Just typing out loud really to document some thoughts and attempts.

             

            If I strip out the web module portion of the ear (update application.xml, remove unused jars, delete the WAR), the EJB portion deploys with no problems.

             

            One thing that may be pertinent, I remembered I've got the JSF bundled with my WAR.  So I removed the jsf-impl and jsf-api files from the manifest.  It doesn't seem to have made a difference.

            • 3. Re: Deploying as an Ear File
              William Lovett Newbie

              I thought I'd test if the war is the problem so I created another bare bones WAR out of a dynamic web project with one JSP and added it to my ear.  It does not have a dependency on the ejb jar.  I also removed the initial war from the ear. 

               

              No luck on fixing the deployment.  Same problem occurs.  Also, for both setups, if I let the deployment run, I get some additional INFO messages in the server.log

               

              17:02:35,679 WARN  [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014626: Operation was interrupted before stability could be reached
              17:03:11,075 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "null" (runtime-name: "MyMultiEJB.jar")
              17:03:11,075 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "null" (runtime-name: "TestWar.war")
              17:03:15,225 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment null (runtime-name: MyMultiEJB.jar) in 4154ms
              17:03:15,240 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment null (runtime-name: TestWar.war) in 4165ms
              17:03:15,552 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment MyMultiTest.ear (runtime-name: MyMultiTest.ear) in 39872ms
              
              • 4. Re: Deploying as an Ear File
                Stephen Coy Master

                Please attach a complete server.log.

                 

                Tip: Click on "Use advanced editor" on the right of the reply panel to get access to file attachments.

                • 6. Re: Deploying as an Ear File
                  William Lovett Newbie

                  Boing!

                   

                  I'm open to ideas not involving Manifest files if that makes a difference.  Those are just easy to setup in Eclipse.

                  • 7. Re: Deploying as an Ear File
                    Stephen Coy Master

                    This looks like it's timing out after ten minutes.

                    08:57:46,695 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of "MyMultiTest.ear" (runtime-name: "MyMultiTest.ear")

                    09:07:46,703 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "MyMultiTest.ear" was rolled back with ...

                     

                    At one point the default was 60 seconds, so maybe you've configured it for ten minutes?

                     

                    You said earlier it normally takes your WAR 20 minutes to deploy.

                    • 8. Re: Deploying as an Ear File
                      William Lovett Newbie

                      Haha.  I was logging back on to say it was a timeout issue but it looks like you've beat me to it. 

                       

                      I can deploy through the admin console and it works fine.  Deploying by dragging and dropping the files into the deployments folder causes the timeout problem.