Troubleshooting synchronization problems

To resolve a problem, you must collect as much information as possible about a problem. Common synchronization issues that require additional information include blocked synchronizations and error messages that do not display long enough to be read.

Procedure

  • When a synchronized stream has a status of Blocked in the ClearCase-Synchronized Streams view, the most recent synchronization request has been blocked. You can get more information about why it has been blocked by viewing the latest synchronization results. To get information about a blocked synchronization:
    1. Right-click the stream in the ClearCase Synchronized Streams view and click Open Latest Synchronization Details.
    2. In the editor, go to the Logs page and open the Full Build Log.
  • Sometimes the synchronization engine window closes immediately after an error message is displayed, which prevents you from reading the message. When that occurs, you can create a script to run the Jazz® Build Engine in an existing window. Create this script by completing the following steps:
    1. Locate the synchronization startup script. The location of the directory that contains the script is displayed in the Jazz Provider Properties page as the value of the STREAM_SCRIPT_DIR argument. The script has the same name as the synchronized stream. For example, script_location_prefix_value/synchronization_stream_name.
    2. Create a copy of the script.
    3. Edit the copy by removing the first few words, up to the path name to the Jazz Build Engine.
    4. Run the copy of the script.
    When the Jazz Build Engine reports an error and exits, the messages are displayed in the window in the script window.

What to do next

Review any error messages and logs to determine what the problem is. For a list of common problems and suggested workarounds, see Synchronization errors. Fix the problem, and then run the synchronize operation again. The new synchronization starts from the last synchronization root that was successfully synchronized during the failed or blocked attempt.

Note: In addition to the message in the log, a synchronization stack trace log is created for the error. This log provides additional information that can help IBM® Software Support interpret the error and resolve the problem. When reporting a problem, include a description of how to reproduce the failure and attach the stack trace log.