Enterprise Application .ear fails when deployed from both the administrative console and wsadmin
 Technote (troubleshooting)
 
Problem(Abstract)
When migrating an Enterprise Application .ear from WebSphere Application Server V4.0.x to WebSphere Application Server V5.x, the .ear deployment fails from both the administrative console as well as from the wsadmin scripting tool.

The following error message is displayed in the administrative console:

Error 500
An error occurred while processing request: /admin/defaultBindings.do
Message:

AppDeploymentException: [ADMA0092E: Unexpected exception occurred while preparing task CorrectOracleIsolationLevel. Please check server machines FFDC for more information.]
AppDeploymentException: []
java.lang.NullPointerException
AppDeploymentException: []
java.lang.NullPointerException
java.lang.NullPointerException
at
com.ibm.ws.management.application.client.AppInstallHelper.getModuleConfig(AppInstallHelper.java:230)
at
com.ibm.websphere.management.application.client.ArchiveDeploymentInfo.createModuleConfig(ArchiveDeploymentInfo.java:138)
at
com.ibm.websphere.management.application.client.AppDeploymentInfo.getModuleConfig(AppDeploymentInfo.java:204)
at
com.ibm.ws.management.application.client.CorrectOracleIsolationLevelHelper.prepareForWAR(CorrectOracleIsolationLevelHelper.java:146)
at
com.ibm.ws.management.application.client.CorrectOracleIsolationLevelHelper.prepareTask(CorrectOracleIsolationLevelHelper.java:89)
at
com.ibm.websphere.management.application.client.AppDeploymentController.prepareTask(AppDeploymentController.java:541)
at
com.ibm.websphere.management.application.client.AppDeploymentController.getNthTask(AppDeploymentController.java:522)
at
com.ibm.websphere.management.application.client.AppDeploymentController.getTaskByName(AppDeploymentController.java:579)
at
com.ibm.ws.management.application.client.MapResRefToEJBDependencyHelper.setupDependency(MapResRefToEJBDependencyHelper.java:33)
at
com.ibm.websphere.management.application.client.AppDeploymentController.getDependencyTask(AppDeploymentController.java:607)
at
com.ibm.websphere.management.application.client.AppDeploymentController.getNthTask(AppDeploymentController.java:525)
at
com.ibm.websphere.management.application.client.AppDeploymentController.getNextTask(AppDeploymentController.java:558)
at
com.ibm.ws.console.appmanagement.action.GatherTaskData.execute(GatherTaskData.java:134)
at
com.ibm.ws.console.appmanagement.action.DefaultBindingsAction.perform(DefaultBindingsAction.java:193)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:267)
at
com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:229)
at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:137)
at
com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:249)
at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispa
tch(WebAppRequestDispatcher.java:1023)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:561)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:198)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:212)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
 
Cause
One of the IBM extension files is corrupt because it is missing the webApp tag.
 
Resolving the problem

What WebSphere Application Server is doing during deployment

WebSphere Application Server obtains the .ear file from either a local or remote path. Behind the scenes it attempts to verify the XMI extensions and bindings; however, one of the extension binding files cannot find a needed reference to the Web application and fails with a null value error.

Upon examination, using Application Server Toolkit (ASTk), of the client's original .ear file, there is an ibm-web-ext.xmi file that did not contain a reference for the webapp tag.

original ibm-web-ext.xmi file

<webappext:WebAppExtension xmi:version="2.0"
xmlns:xmi="http: //www.omg.org/XMI" xmlns:webappext="webappext.xmi"
xmlns:xsi="http: //www.w3.org/2001/XMLSchema-instance"
xmi:id="WebAppExtension_1" reloadInterval="3" reloadingEnabled="false"
fileServingEnabled="true" directoryBrowsingEnabled="false"
serveServletsByClassnameEnabled="false" preCompileJSPs="false">
<defaultErrorPage xsi:nil="true"/>
<additionalClassPath xsi:nil="true"/>
</webappext:WebAppExtension>

To correct the problem, import the .ear into ASTK and modify the ibm-web-ext.xmi file. Add the following:

<webApp href="WEB-INF/web.xml#WebApp_ID"/>

updated ibm-web-ext.xmi file:

<webappext:WebAppExtension xmi:version="2.0"
xmlns:xmi="http: //www.omg.org/XMI" xmlns:webappext="webappext.xmi"
xmlns:xsi="http: //www.w3.org/2001/XMLSchema-instance"
xmi:id="WebAppExtension_1" reloadInterval="3" reloadingEnabled="false"
fileServingEnabled="true" directoryBrowsingEnabled="false"
serveServletsByClassnameEnabled="false" preCompileJSPs="false">
<defaultErrorPage xsi:nil="true"/>
<additionalClassPath xsi:nil="true"/>
<webApp href="WEB-INF/web.xml#WebApp_ID"/>
</webappext:WebAppExtension>

Save the file and export the .ear from ASTk.


You can now use the administrative console or wsadmin to deploy the .ear file.

Note: You do not have to use ASTk. This is the tool that the WebSphere Application Support team uses when doing problem determination. You can use the Application Assembly Tool (AAT) for v5.0.x; however it is deprecated from 5.1.x and replaced with ASTk.

If this does not resolve the problem, please refer to the below document prior to opening a new PMR with the support team.

Refer to MustGather: Enterprise Application Archives and Application Assembly Tool Problems for all Releases of V4.0 and V5.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
25754 379 000
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Deploy (for example: AAT or ANT or EAR/WAR/JAR)
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1170362
IBM Group: Software Group
Modified date: May 28, 2004