[defiant42]

Am trying to deploy an EAR application to a WAS 6.1.0.17 Server, and am getting the following exception during the -ejbdeploy task:

The odd thing is I’VE REMOVED the offending .jar file (ServiceLocator.jar) from the EAR-Project/Lib directory, and cannot find it under the Web-Project in the WEB-INF/Lib directory.

Using another EAR Project that contains ONLY my EJB Project, and it deploys fine.

Back to the original project, If I comment out the Web Module reference in the application.xml, it deploys fine. I blew away the WEB Project, and re-added from a backup a while back, [when it used to work 🙂 ] and still get the IWAE0015E exception…

The thing that I changed was to modify the Web-Project to reference the ServiceLocator project directly instead of using the .jar file. That-way I can debug it….

ME Blue install info is below.

Eric

—————————————————————————————————————————————
MyEclipse: deployment START explodedproject: ERC_TEST_EAR server: websphere61Server#Server1P4ERCTNG time: Tue Aug 26 09:29:53 CDT 2008
—————————————————————————————————————————————
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[C:\apps\IBM\WebSphere\AppServer6.1\profiles\AppSrv04\installableApps\ERC_TEST_EAR.ear, SSHMSG242LAP013Node03Cell, SSHMSG242LAP013Node03, server1, ERC_TEST_EAR, {{“ERC_TEST_WEB.war” “ERC_TEST_WEB.war,WEB-INF/web.xml” default_host}}, {{“null” “ERC_TEST_WEB.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}, false, true, true, C:/apps/MyEclipse6.5Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere_6.5.0.zmyeclipse650200806/scriptutil/scriptutil.jar, C:/apps/IBM/WebSphere/AppServer6.1/profiles/AppSrv04/installedApps/SSHMSG242LAP013Node03Cell/ERC_TEST_EAR.ear/ERC_TEST_EJB.jar]”
C:\apps\IBM\WebSphere\AppServer6.1\profiles\AppSrv04\installableApps\ERC_TEST_EAR.ear
SSHMSG242LAP013Node03Cell
SSHMSG242LAP013Node03
server1
ERC_TEST_EAR
{“ERC_TEST_WEB.war” “ERC_TEST_WEB.war,WEB-INF/web.xml” default_host}
{“null” “ERC_TEST_WEB.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -useMetaDataFromBinary -deployejb -appname “ERC_TEST_EAR” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -noprocessEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“ERC_TEST_WEB.war” “ERC_TEST_WEB.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{“null” “ERC_TEST_WEB.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}
false
true
true
C:/apps/MyEclipse6.5Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere_6.5.0.zmyeclipse650200806/scriptutil/scriptutil.jar
C:/apps/IBM/WebSphere/AppServer6.1/profiles/AppSrv04/installedApps/SSHMSG242LAP013Node03Cell/ERC_TEST_EAR.ear/ERC_TEST_EJB.jar
-deployejb
WASX7017E: Exception received while running file “C:\apps\MyEclipse6.5Blue\myeclipse\eclipse\plugins\com.genuitec.eclipse.blue.websphere61_6.5.1.zmyeclipse650200806\installEAR.jacl”; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: AppDeploymentException: []
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.ManifestException: IWAE0015E An IOException occurred reading the manifest in archive: WEB-INF/lib/servicelocator.jar
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.ManifestException: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.ManifestException: IWAE0015E An IOException occurred reading the manifest in archive: WEB-INF/lib/servicelocator.jar

*** Date:
Tuesday, August 26, 2008 9:39:28 AM CDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_14

*** MyEclipse details:
MyEclipse Blue Edition
Version: 6.5.1 Blue GA
Build id: 6.5.1-Blue-GA-20080715

*** Eclipse details:
MyEclipse Blue Edition

Version: 6.5.1 Blue GA
Build id: 6.5.1-Blue-GA-20080715

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\apps\MyEclipse6.5Blue\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\apps\MyEclipse6.5Blue\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\apps\MyEclipse6.5Blue\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
b64_78
-clean
-showlocation
-data
C:\dev\eclipse\ws8
-vmargs
-Xmx1536m
-vm
C:\apps\MyEclipse6.5Blue\jre\bin\javaw.exe

[Loyal Water]

Moving to MyEclipse BLue IDE >> General

I have asked someone from the dev team to look into this issue. They will get back to you with an update asap.

[defiant42]

Thanks! I’ve noticed that manipulating the settings at the EAR & WAR project level with regard to how deployments are used (namely Web-SmartDeploy), has an effect. Then the manifest error goes away, but then I get classloader errors on classes that cannot be found by the web-tier….

Eric

[Loyal Water]

Eric,
Can you send us a sample project that would help us reproduce this issue. You can hit the *pm* button at the bottom of my post and send me the project.

[defiant42]

At this time, I’ve got the problem solved, and I do not have the project in ~that state~ anymore. What I ended up doing was:

1) Workbench Settings
MyEclipse Blue->Java Enterprise Project->EAR Project Set Jar dependant Java Projects ON.
MyEclipse Blue->Java Enterprise Project->EJB Project Deployment Tab Set Ignore ON.
MyEclipse Blue->Java Enterprise Project->WEB Project Deployment Tab Set Ignore ON.

2) For my EAR Project
Properties->MyEclipseBlue->EAR
Set Jar Dependant Java Projects ON
Jars exported from dependant Java Projects CHECKED.
Set Automatically update ‘application.xml’ as needed ON.

3) For my WEB & EJB Projects
Properties->MyEclipseBlue->EJB-> Deployment
Properties->MyEclipseBlue->WEB->Deployment
Set these to use the Workbench default settings.

4) Making the settings above got all of my dependant projects jar’d, as well as going to the EARProject->Properties->Project References, and CHECKING ALL the projects,
gets them placed in the ROOT of the EAR. I verified this once deployed to the Server. Again, these need to ALL BE JAR’D and placed in the root of the ear. NOT
A /Lib directory in the ear, BUT THE ROOT OF THE EAR.

5) Went back to the WEB Project & EJB Project and made sure I had the correct dependant projects EXPORTED [so the mainifest.mf files] will have the correct entries.
Also removed ALL exported entries from the dependant projects that rolled up under the Web-Tier. Earlier I had some jars flagged for export, and ended up with
duplicate entries in the manifest.mf for the WAR, which resulted in an exception during deployment. One that had good wording at that!

6) Once I had all the export settings correct, I manually & FORCEFULLY DELETED ALL MANIFEST.MF files under ALL the projects. One of the projects that I was using had
an manifest.mf file that was created under WSAD, and was blank. However, I did figure out that this file had something corrupt about it, and was set to read-only, so MEB
could not change it, but caused and exception when it tried to load it. Next went to the EAR Project->MyEclipse->New Module Manifests, re-genned all the manifest.mf files,
then eye-balled ALL OF THEM, to make sure they had the correct entries.

7) With these steps, I was able to get the projects to deploy correctly, AND, [YES AND] was able to step through and debug them interactively….I never did figure out how/why I was getting a rough version of the corrupted manifest.mf file under /WEB-INF/Lib/servicelocator.jar That was weird….

Eric

[Loyal Water]

Eric,
Thank you for posting this information. I’m glad you got it to work and I hope you don’t run into such weird issues again.

[Author]

Posts