TroubleShooting: Synchronization problems
 Technote (troubleshooting)
 
Problem(Abstract)
This is a troubleshooting guide for synchronization for V5.0, V5.1 and V6.0 issues in the IBM® WebSphere® Application Server product. This should help address common issues with this component.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data 4. Analyzing data

Steps to help resolve Synchronization problems

  1. What is the state of the node(s)? (check the administrative console)
    1. Unknown or unavailable
      • Is the nodeagent running?
        • Yes, this is a discovery problem not a synchronization problem, see discovery TroubleShooting
        • No, start the nodeagent, this process is required for synchronization to work.

    2. Not synchronized, continue to step 2.

  2. Is the "filetransfer" application installed and running? (Go to Applications > Enterprise Applications in the administration console to view installed and running applications)
    • If not installed, follow this technote to reinstall.
    • If stopped, start the "filetransfer" application. Continue to step 3 if problem is not resolved

  3. If you just enabled security, were all WebSphere Application Server processes (dmgr, nodes, appservers) recycled enabled?
    • Yes, continue to step 5.
    • No, recycle all processes then attempt to synchronize the node with the syncNode command. If the problem continues, go to step 5.

  4. Do you see the following error within the NodeAgent SystemOut.log file?

    NodeSyncTask  A ADMS0016I: Configuration synchronization failed.NodeSync E ADMS0005E: Unable to generate synchronization request: javax.management.RuntimeMBeanException at com.ibm.ws.management.connector.soap.SOAPConnectorClient. handleAdminFault(SOAPConnectorClient.java(Compiled Code))....

    • Yes, see this technote on how to correct the problem.
    • No, go to the next step.

  5. Do you see the following error within the NodeAgent SystemOut.log file?

    ADMD0012E: Unable to initialize the transport of type: TCP
    ADMS0012E: Unable to create administrative client connection:
    com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable

    • Yes, see this technote.
    • No, go to the next step.

  6. Do you see the following error within the NodeAgent SystemOut.log file?

    ADFS0119E: An unexpected exception occurred: java.io.EOFException: Unexpected end of  ZLIB input stream

    • Yes, see this technote.
    • No, go to the next step.

  7. Do you see the following error within the NodeAgent SystemOut.log file?

    ADMS0005E: Unable to generate synchronization request: javax.management.RuntimeMBeanException: Prefix string too short

    • Yes, see this technote.
    • No, go to next step.

  8. Do you see the following error within the NodeAgent SystemOut.log file?

    ADMS0005E: Unable to generate synchronization request: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke

    • Yes, see this technote
    • No, see the following What to do next? section.


What to do next?
If the preceding troublehooting steps did not solve your problem, see the MustGather for synchronization problems to continue investigation.
 
Related information
Submitting information to IBM Support
Steps to getting support
Troubleshooting guide
 
 
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 > System Management/Repository
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1199305
IBM Group: Software Group
Modified date: Feb 8, 2006