WAS 7 - EAR Deployment Error

--------------------------------

We have been deploying the same ear file on WAS 6.1. But deploying it on WAS 7 fails deployment (we check deploy enterprise beans option).

Following is the error encountered:
Check the SystemOut.log on the deployment manager or server where the application is deployed for specific information about the EJB deployment process as it occurs.
ADMA5016I: Installation of ClientApplication started.
ADMA5067I: Resource validation for application ClientApplication completed successfully.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5018I: The EJBDeploy program is running on file /opt/WAS7/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp/514564614/upload/ClientApplication.ear.
Starting workbench.
EJB Deploy configuration directory: /opt/WAS7/IBM/WebSphere/AppServer/profiles/AppSrv01/ejbdeploy/configuration/
framework search path: /opt/WAS7/IBM/WebSphere/AppServer/deploytool/itp/plugins
Creating the project.
*** ERROR ***: Fri Jan 23 17:39:58 PKT 2009 Error loading nested archive: ClientApplicationWeb.war
*** ERROR ***: Fri Jan 23 17:39:58 PKT 2009 java.lang.NullPointerException
org.eclipse.core.commands.ExecutionException:
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.importEar(BatchExtension.java:1095)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtension.java:354)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.access$1(BatchExtension.java:349)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtension.java:332)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExtension.java:297)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:260)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:484)
at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:100)
at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:104)
at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:334)
Jan 23, 2009 5:39:58 PM com.ibm

I can advise you what is happening, but it might not help...

--------------------------------

When you deploy an application to WAS from WAS6.1 onwards there is a lot of dynamic work that happens under the covers. With the EJB3 Feature Pack on WAS6.1 and WAS7 there is a lot of extra checking that goes on because of annotations. It is possible that this checking is causing the issue, but it would require some checking.

The EJB Container, and the EJS Container workhorse that it delegates to, have listeners for deployments and subscribe to the Application Manager Service inside WAS. When you deploy anything to WAS the Application Manager Service sends out Deployment Event Notifications to the subscribers that contain an event and reference to the application and its modules. The containers then open the EAR, WAR, and EJB-JAR files and scan the contents for deployment information in XML files or in annotations in the code itself. this enables WAS to generate its own deployment metadata, configuration and supporting runtime code to support the target application.

I haven't seen this specific error here, but have seen similar errors with web services where there is something in the XML DD that disagrees with something else that may be in an annotation that wasn't scanned before.

Does this help at all?

--------------------------------

Posted By: ColinRenouf at Feb 21 2009 12:39AM