Deploying as an Ear File using Manifests. JBAS014862: Operation cancelled
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?
