In rare circumstances, when you run the repository tools -rebuildTextIndices command, the system might take a long time to respond or appear to hang. This issue occurs when text in a work item or work item attachment contains very long lines of text with no spaces, such as text that is hundreds or thousands of characters long.

In newer versions of CLM -  603ifix5, 602ifix11, and 502ifix21 - the problem is fixed. In these versions, long lines with no spaces, are skipped if they are longer than 2000 characters.

If you want to consider these long lines for stack trace analysis, see below.

1. For each server that is running an instance of the CCM or QM application, open the repotools-application.bat file.

Here are the relevant batch files.
Change and Configuration Management (CCM): repotools-ccm.bat
Quality Management (QM): repotools-qm.bat

2. In the file, find this line:
set DEFINE=%DEFINE_INIT%

3. After the line, add these lines:
set DEFINE=%DEFINE% "-Dcom.ibm.team.repository.restrictStackTraceLineLength=false"
set DEFINE=%DEFINE% "-Dcom.ibm.team.repository.stackTraceLineLength=2000"

When this system property is set to true, any lines with no spaces longer than 2000 characters will be skipped during indexing. To adjust the default character limit, change the value of -Dcom.ibm.team.repository.stackTraceLineLength to an integer. If the value is set to 0, stack trace analysis will be skipped.

4. (Optional) For each server that is running an instance of the CCM or QM application and has to be updated, complete the steps based on the type of application server:

For WebSphere Application Server:
a. Use the web console to go to Application servers > server 1 > Process definition > Java Virtual Machine.
b. Add the following lines to the Generic JVM arguments settings.
-Dcom.ibm.team.repository.restrictStackTraceLineLength=false
-Dcom.ibm.team.repository.stackTraceLineLength=2000

5. Run repotools-application.bat -rebuildTextIndices.

If -Dcom.ibm.team.repository.restrictStackTraceLineLength is set to true, lines that are longer than the specified character limit are skipped during indexing.
If debugging is enabled, the repotools-application_rebuildTextIndices log file and the console show information about the affected artifact and lines.

Example:
Indexing document belonging to artifact : 10: Stacktrace Defect , of type : com.ibm.team.workitem.WorkItem
Skipping the regex matching for line : [9/10/14 0:30:43:558 CEST] 00000101 id=        ca..   of length : 2500
Skipping the regex matching for line : [9/10/14 0:31:44:557 CEST] 00000102 id=         c... ;  of length : 17838