Troubleshooting
Problem
If you launch the scm.exe command in IBM Rational Team Concert, you will observe that the command never terminates.
Symptom
You invoke a comparison, for example you compare a Workspace and a Snapshot, with a command line like the following:
C:\Program Files\IBM\TeamConcert\scmtools\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazz workspace "MyWorkspace" snapshot "Snapshot1" -I f
The command then never terminates: it hangs indefinitely.
Perform the following steps to capture log data to be used to troubleshoot the hanging behavior:
1. Open the file scm.ini, typically located in:
C:\Program Files\IBM\TeamConcert\scmtools\eclipse\scm.ini
The contents of the file look like the following:
-vm |
2. Change directory to the parent folder of java.exe.
From that directory, run java -version and save the output in a text file.
The output will indicate if the JVM is an IBM JVM.
3. The Steps 3-5 are only applicable to the IBM JVM.
If you are using another JVM, then you will need to consult the documentation supplied by its vendor.
Open scm.ini and add the following parameters, each on a separate line, starting after the line that contains vmargs:
-Xdump:java+system:events=user-verbose:gc -Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt |
The contents of
scm.ini should then look like this:-vmC:\Program Files\IBM\TeamConcert\jdk\jre/bin/java.exe --launcher.suppressErrors -data @noDefault -vmargs -Xdump:java+system:events=user -verbose:gc -Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt -Xmx512m -Xshareclasses -Xquickstart -Dosgi.requiredJavaVersion=1.5 |
After you do this, launch the hanging operation, for example:
C:\Program Files\IBM\TeamConcert\scmtools\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazz workspace "MyWorkspace" snapshot "Snapshot1" -I fIn the same command window where the above command is running, type:
CTRL+BREAKThis sends a signal to the JVM and it writes the following:
JVMDUMP006I Processing dump event "user", detail "" - please wait.
JVMDUMP032I JVM requested System dump using
'C:\Program Files\IBM\TeamConcert\scmtools\eclipse\core.20111018.121358.3896.0001.dmp'
in response to an event
C:\Program Files\IBM\TeamConcert\scmtools\eclipse>JVMDUMP010I System dump written to C:\Program Files\IBM\TeamConcert\scmtools\eclipse\core.20111018.121358.3896.0001.dmp JVMDUMP032I JVM requested Java dump using
'C:\Program Files\IBM\TeamConcert\scmtools\eclipse\javacore.20111018.121358.3896.0002.txt'
in response to an event
JVMDUMP010I Java dump written to
C:\Program Files\IBM\TeamConcert\scmtools\eclipse\javacore.20111018.121358.3896.0002.txt
JVMDUMP013I Processed dump event "user", detail "".
/Project1/src/com/Class3.java
/Project1/src/com/If1.java The output indicates that the following files were created:
| File Name | Purpose |
verbosegc.20111018.122106.3848.txt | Verbose Garbage Collector log. |
javacore.20111018.121358.3896.0002.txt | Text file thatcontains the list of all threads. |
core.20111018.121358.3896.0001.dmp | System core dump. |
4. For an IBM JDK versions 1.6 and lower, you must process the system core dump with the jextract utility before submitting it to support.
This is the syntax of the jextract command:
<installroot>/jre/bin/jextract [corefile]
The
jextract command produces a jar file.5. Repeat the steps 3-4 a few times at a distance of a few minutes.
6. Collect the out output of the command:
netstat -an > netstat.log
7. Configure Command Line Interface tracing as discussed in the following article: Default logging for CLI
Resolving The Problem
Submit the following artifacts to IBM Rational Client Support for investigation:
- Output of
java -version - Verbose Garbage Collector Log
javacorefilescorefile (processed withjextract)- Output of the
netstat -ancommand - Provide the output of the Command Line interface trace.
Related Information
Product Synonym
Rational Team Concert
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21572522