IBM Support

Unable to deploy application EAR file using the administrative console

Troubleshooting


Problem

Application deployment fails when using the administrative console. The administrative console shows the following message.  Messages Application already exists in the config repository.

Cause

The XYZ.ear has an application.xml with an application display-name that is the same, as an existing application.

XYZ.ear
application.xml
Dmgr - SystemOut.log shows following error
[4/14/05 13:06:13:505 PDT] 5c7d8d36 WebGroup I SRVE0180I: [adminconsole] [/admin] [Servlet.LOG]: action: ApplicationDeploymentDetailForm was null.Creating new form bean and storing in session
[4/14/05 13:06:13:771 PDT] 5c798d36 SRTServletRes E SRVE0120E: IO Error java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java(Compiled Code))
at java.net.SocketOutputStream.write(SocketOutputStream.java(Compiled Code))
at com.ibm.ws.io.Stream.write(Stream.java(Compiled Code))
at com.ibm.ws.io.WriteStream.flushMyBuf(WriteStream.java(Inlined Compiled Code))
at com.ibm.ws.io.WriteStream.flush(WriteStream.java(Inlined Compiled Code))
at com.ibm.ws.http.ResponseStream.flush(ResponseStream.java(Compiled Code))
at com.ibm.ws.io.WriteStream.flush(WriteStream.java(Compiled Code))
at com.ibm.ws.webcontainer.http.HttpConnection.flush(HttpConnection.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.srp.SRPConnection.flush(SRPConnection.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.SRTOutputStream.flush(SRTOutputStream.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.flushBytes(BufferedServletOutputStream.java:370)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.flush(BufferedServletOutputStream.java:343)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.finish(BufferedServletOutputStream.java:169)
at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.close(BufferedServletOutputStream.java:433)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.closeResponseOutput(SRTServletResponse.java:1344)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
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))

Resolving The Problem

Things to validate:
  1. Validate that each serverindex.xml file from the primary repository, has no reference to the XYZ application.
     
  2. Validate that each node-binary installation has no reference to the XYZ application.

    Note: <WAS_INSTAL_ROOT>/profiles/<profileName>/InstalledApps/<cellName>
     
  3. Validate that each config/cells/<cellname>/application directory, has no reference to the XYZ application.

If the above steps are validated successfully and problem still persists then it is possible the cause is the application ear itself.

Example:
XYZ.ear
application.xml in meta-inf has following reference

  
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application id="Application_ID">
    <display-name>DefaultEAR</display-name>
    <module id="WebModule_1110326143477">
          <web>
                <web-uri>xyz.war</web-uri>
                <context-root>service</context-root>
          </web>
    </module>
</application>



As you can see the display name is incorrect in display-name tag. This is the reason why the application cannot be deployed. The deployment process thinks that XYZ exists in the Applications > Enterprise Applications > Enterprise Applications list.

In this case you did have a DefaultEAR deployed so application deployment was failing, which indicated the application already exists.

To correct this:
  1. Import the application into the Development Tool of choice.
     
  2. Correct the application.xml display-name tag.
     
  3. Export the application.
     
  4. Try deploying the application using the administrative console.
     
  5. If this fails then collect MustGather information and open a PMR with IBM Support.
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg21145599

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Administrative Console (all non-scripting)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0","Edition":"Base;Enterprise;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 April 2022

UID

swg21203410

Page Feedback