This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 754101

Summary: (EAP 5.1.x admin-console) Exploded deployment of an EAR not containing MANIFEST.MF causes error
Product: [Other] RHQ Project Reporter: Jan Martiska <jmartisk>
Component: PluginsAssignee: Larry O'Leary <loleary>
Status: CLOSED WORKSFORME QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0.0CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 16:47:56 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Jan Martiska 2011-11-15 07:18:46 EST
This issue applies to EAP 5.1.2 ER2.

When you use the admin console to deploy (in exploded form) an EAR that does not contain META-INF/MANIFEST.MF file, you will see an error like this>

Failed to create Resource mock-ear.ear - cause: (No such file or directory)

The EAR application (at least in my case) still gets deployed properly, but this error message might cause confusion to the user.

Full stacktrace from the EAP log: /home/jmartisk/builds/jboss-eap-noauth-5.1.2-ER2/jboss-as/server/default/deploy/mock-ear.ear/META-INF/MANIFEST.MF (No such file or directory)
at Method)
at org.rhq.plugins.jbossas5.deploy.AbstractDeployer.deploy(
at org.rhq.plugins.jbossas5.helper.CreateChildResourceFacetDelegate.createContentBasedResource(
at org.rhq.plugins.jbossas5.helper.CreateChildResourceFacetDelegate.createResource(
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.rhq.core.pc.inventory.ResourceContainer$
at java.util.concurrent.FutureTask$Sync.innerRun(
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
at java.util.concurrent.ThreadPoolExecutor$
Comment 1 Larry O'Leary 2013-02-14 16:47:56 EST
I retested this in EAP 5.2 and did not see the error.

Closing as WORKSFORME as there is no RHQ specific action to take at this point. If this issue still exists in admin-console we should get downstream JBPAPP-7526 cloned to EMBJOPR JIRA.