IBM Support

MustGather: Source Control issues with Rational Team Concert

Technote (troubleshooting)


How to collect the data necessary to diagnose and resolve IBM Rational Team Concert (RTC) source control issues.


This MustGather will assist you in collecting the data necessary to help you diagnose and resolve the issue. If you are unable to determine the root cause using the information collected, you should open a PMR with IBM Support for further investigation providing the data collected.

Resolving the problem

You can use the IBM Support Assistant Lite (ISA Lite) Data Collector tool to quickly collect diagnostic files, such as log files, configuration files or to run traces. This tool is bundled with RTC 4.x and above. ISA Lite collects information about your Jazz Team Server environment and stores the information in a .zip archive file. If you have a need to open a service request with IBM Support for further assistance, you can send the archive file with the data collection so that they can help diagnose and fix problems.

The information below should be gathered in addition to the normal information and log gathering done by ISA Lite.

SCM Data Transfer Issues

When there is difficulty with transferring data between the server and the client such a timeouts, out of memory errors or general slowness collect the following data.


Enable Verbose Garbage Collection in WebSphere
    In the Administrative Console, expand Servers, expand Server Types, and then click WebSphere application servers.
    Click on the server that you would like to work with, for example, server1.
    On the Configuration tab, under Server Infrastructure, expand Java and Process Management, and click Process Definition.
    Under the Additional Properties section, click Java Virtual Machine.
    Check the Verbose Garbage Collection check box.
    Apply and Save the changes.

Enable the JVM to create javacores in WebSphere
    From the Additional Properties section add the following to the Generic JVM arguments
    Apply and Save the changes.

    Note: If either heap or system options are already present they should be removed
    -Xdump:java+ heap + system :events=user

    Restart the Application Server for the previous two changes to take effect.

Enable the JVM to create javacores and verbose GC logging in Tomcat
    Add the following two lines to the server.startup script or to the Java Options in the Tomcat Control Panel if running as a Windows Service.
    Restart the Application Server for the changes to take effect.

Note: Both the previous settings should be safe to leave enabled at all times. Garbage collection has a minimal impact on the server and Xdump has no impact unless explicitly called.

    Data Collection
      The following do not need to be done in any particular order but because they will create significant additional logs it is recommended they be preformed reasonably close to the time of the reproduction.

    Note: Because of the amount of logs generated by the following two settings it is recommended that they be disabled after reproducing the problem.

    Enable SCM Service Logging
      From the /ccm/admin page click on Advanced in the right hand column
      Search for "Enable SCM Service Logging"
      Set to true
      Scroll to the top of the page and click Save
      You should see Configuration changes saved successfully message.
      A restart is not required.
      Disable when the reproduction is complete.

    Enable SCM and SQL tracing
      Add the following lines to <server-install-dir>/server/conf/ccm/
      Enable these settings without restarting
      From the following URL
      https:// <server:port> / ccm /admin?internal=true

      Select Reload Log Settings on the left side under Internal Tools,
      Disable when reproduction is complete

        To disable you must replace TRACE and DEBUG with OFF and use the Reload Log Settings operation again.
        Removing them or commenting them out will prevent them from being disabled.

    Start the WAIT script
      Run the script in 60 second intervals with enough iterations to cover the time of the reproduction with a few minutes before and after.
      Collect data at 1 minute interval with 40 iterations use the following arguments: --sleep 60 --iters 40 <CCM-WAS-PID>

      Note the iters argument can be removed to run the tool until it is stopped manually with CTL\C
      Warning: The WAIT tool will detect if your JVM is set to collect heapdumps or system core files and will require special arguments to run if either of these are enabled.
      Running the tool with theses options set will cause severe performance degradation and should only be used when expressly requested by IBM support.

    Use the Query Stats counter service to gather query stats.
      From the following link:
      Find and follow

      Press the Reset Query Stats link then the Start Collecting Query Stats link.
      Reproduce the problem

      To save, browse to the Query Stats View, copy and save the output to an ASCII file

    Reproduce the problem, collect and send in the following:
      ISAlite data
        This will include the logs containing the SCM and SQL traces.
      The Query Stats output from the Query Stats View saved to an ASCII file
      The WAIT output.

    4.x Data Collection tool
    3.x Data Collection tool
    2.x Data Collection tool

    SCM CLI (Command Line Interface)

    • Can this issue be reproduced in the Eclipse client (not using the CLI) or web US (User Interface)?

    SCM Eclipse Client

    • Collect the relevant screenshots

    • Collect the workspace log file located in ‘workspace directory/metadata’ named .log

    SCM Web UI
    • Collect the relevant screenshots

    SCM Additional Resources

    Leverage the Jazz Community

    Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.
    Refer to technote 1319600 for details and links.

    Document information

    More support for: Rational Team Concert

    Software version: 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7

    Operating system(s): AIX, Linux, Solaris, Windows

    Reference #: 1632546

    Modified date: 26 September 2014

    Translate this page: