Unable to deployed application EAR file via adminconsole
 Technote (troubleshooting)
 
Problem(Abstract)
Application deployment fails when using the adminconsole. The adminconsole shows the following message.

Message(s)
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 master repository, has no reference to the XYZ application.
  2. Validate that each node binary installation has no reference to the XYZ application.

    Note: v5 and v5.1 <install_root>/InstalledApps

    Note: v6 <install_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 can not be deployed. The deployment process thinks that XYZ already exits in

Applications -> Enterprise Applications -> Enterprise Applications list.

In this case we did have a DefaultEAR deployed so application deployment was failing indicating that the application already exits.

To correct this:

1. Import the application into the Application Assembly tool kit (ASTK)

2. Correct the application.xml display name tag.

3. Export the application

Try deploying the application via the adminconsole.

If this fails then please collect our mustgather doc
General/swg21145599.html

And open a PMR with IBM support.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1203410
IBM Group: Software Group
Modified date: Jun 30, 2005