Node fails to synchronize with java.io.IOException: ADMD0004E errors showing in the trace
 Technote (troubleshooting)
 
Problem(Abstract)
A node is failing to synchronize with the Deployment Manager. No errors show in SystemOut or SystemErr logs for either the node or the DeploymentManager, but a discovery trace done on the Deployment Manager shows the following:

[11/12/04 15:08:07:874 EST] 78b6adb6 TcpMessenger d connection refused java.net.ConnectException: A remote host refused an attempted connect operation.
[11/12/04 15:08:08:416 EST] 78b6adb6 DiscoveryServ d IOExceiption occurs while sending messages java.io.IOException: ADMD0004E: Can not open the TCP socket: 7,272
 
Cause
A discrepancy between the contents of the node serverindex.xml file and the servers on the node.
 
Resolving the problem
  1. On the node machine, go to the following directory:

    install_root/config/cells/<cell_name>/nodes/<node_name>/servers

    This directory contains a directory named for each application server on the node. Make note of all the server names you see here.

  2. Back up one directory level to the following directory:

    install_root/config/cells/<cell_name>/nodes/<node_name>

    Locate the serverindex.xml file, make a copy and store it in a safe location.

  3. Open the serverindex.xml file and search for "serverName". You should see an entry for each server you have listed in step 1. If there are additional entries for a server that is not listed in step 1, or an entry for a server is missing, edit the file to correct this.

    For example:
    You have serverA in your servers directory, but there is no section for it in serverindex.xml. In addition, you have a section in serverindex.xml for serverZ, but no directory for serverZ exists. In this case, you would want to change the entry for serverZ in serverindex.xml to serverA. All you need to do is replace the name serverZ with serverA in serverindex.xml.

    If you instead have only an entry for the nonexistent serverZ, and all other servers have an entry, then all you need to do is delete the serverZ entry in serverindex.xml.

    Save your changes.

  4. Substitute the new serverindex.xml file and stop the application servers, nodeagent, and dmgr (in that order).

  5. Restart the dmgr.

  6. Run syncNode from the command line.

  7. Start the nodeagent and application servers.

  8. Open the administrative console and check that the node is synchronized.


Related information
Tracing is done by setting the trace specification to the following:

com.ibm.ws.management.*=all=enabled

For more details, see the following URLs:
 
 
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
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1190624
IBM Group: Software Group
Modified date: Nov 29, 2004