IBM Support

Running Build Forge Project is spawning many ClearCase / ClearQuest UCM integration processes

Technote (troubleshooting)


Attempts to run the IBM Rational Build Forge Project on an IBM Rational ClearCase / Rational ClearQuest UCM configuration result in the spawning of many the CQIntSvr11 processes (cqintsvr11.exe) for each of the BuildForge steps.


Rational Build Forge project step contains the following cleartool commands:

cd /d M:\project1\CVOB\C1

cleartool setact UCM0100000044

cleartool co -nc test1.txt

cleartool ci -nc -identical test1.txt

When Rational Build Forge executes a UCM command (as seen above) through the ClearCase UCM integration to modify ClearQuest using CQIntSvr11, Windows create a new user shell session in which a new instance of CQIntSvr11 (cqintsvr11.exe) is created by Windows.

This instance of cqintsvr11.exe remains in memory even when the Windows user shell session ends.

As more UCM commands are executed by Build Forge, new instances of CQIntSvr11's are created.

These processes remain in memory for as long as Windows is running and eventually consume Windows system resources such that no more CQIntSvr11 instances can be created resulting with the Build Forge command to fail.


This issue was identified as a product defect and logged under APAR PK72842.

The CQIntSvr11 is not designed for a Windows operating system that allows for concurrent user session logon.


ClearCase and ClearQuest UCM environment with Build Forge on the Windows which allow multiple Windows logon session such as Windows 2003 or 2008.

Diagnosing the problem

Open the Windows Task Manager if you see several instances of CQINTSVR11.EXE (or CQINTS~2.EXE) then you are expensing this issue.

Image of Build Forge project and related Task Manager window showing process tree:

Resolving the problem


You can resolve this issue by using one of following workarounds.

Workaround 1 -- Use Rational ClearQuest/ClearCase 7.1.1 REST API (OSLC) architecture

Workaround 2 -- Change windows logon user for Build Forge Agent service

Workaround 3 -- Add a Windows registry key to force a logoff of CQIntSvr11

Workaround 4 -- Continue rebooting the server on a daily basis

Workaround 5 -- Move to a non-Windows OS Platform (For example UNIX platform)

WORKAROUND 1 -- Use Rational ClearQuest/ClearCase 7.1.1 REST API( OSLC) architecture

Using Build Forge project in Rational ClearQuest/ClearCase 7.1.1 environment with Rational ClearQuest REST API (OSLC) integration will by-pass CQIntSvr11. Refer to the details in the technote 1398642 about using the LAN ClearCase/WAN ClearQuest UCM integration that utilizes the ClearQuest OSLC REST interface.

The steps to change to ClearQuest REST API (OSLC) integration setting:

  1. Run the following commands on the ClearCase/ClearQuest UCM machine:

    >crmregister remove -all
    >crmregister add -database test -connection <db_set> -user admin -password "" -url
    http:// :12080/oslc/cqrest

  2. Open http:// :81 on the Rational Build Forge management machine.

  3. Login the Rational Build Forge Management console.

  4. Open Projects > 'Project Name'

  5. Start project and execute

WORKAROUND 2 -- change logon user for Build Forge Agent service

Modify bfdispatch service on any Windows system to run as a particular user. This would ensure that any job run on the client system will assume the credentials of the user that spawned the bfagent process.

Under Control Panel > Administrative Tools > Services > bfdispatch > Logon > Supply a domain qualified Rational ClearCase user that will run the commands you previously listed (recommend to add the local admin rights for the use account on the system.)

This should allow all bfagent processes to run as the desired Rational ClearCase / ClearQuest account and not generate new instance of CQIntSvr11 on Windows.

WORKAROUND 3 -- add a Windows registry key to force a logoff of CQIntSvr11

This workaround instructs SQUID to issue a logoff command to Rational ClearQuest and by doing so forces a termination of CQIntSvr11.


This solution contains information about modifying the system registry. Before making any modifications to the Microsoft Registry Editor, it is strongly recommended that you make a backup of the existing registry. For more information describing how to back up the registry, refer to Microsoft Knowledge Base article 256986

  1. Save the following block of text into a text file called squid_win_auto_logoff.reg

    For a 32 bit host:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\Clearcase Squid]

    For a 64 bit host:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Atria\ClearCase\CurrentVersion\Clearcase Squid]

  2. Double click on the file squid_win_auto_logoff.reg and accept the modification it will make to the Windows registry.

WORKAROUND 4 -- continue rebooting the server on a daily basis

Setup Windows to reboot daily (more or less frequently) to remove all instances of CQIntSvr11's that have built up in memory.

WORKAROUND 5 -- Move to a non-Windows OS Platform (For example UNIX platform)

Since the implementation of CQIntSvr11 on UNIX is a different architecture, CQIntSvr11 does not run into this issue.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational ClearCase Cleartool Windows 7.0, 7.0.1, 7.1, 7.1.1, 7.1.2
Software Development Rational Build Forge Agent: Shell 7.0.2, 7.1, 7.1.1

Document information

More support for: Rational ClearQuest
Integrations: IBM

Software version: 7.0, 7.0.1, 7.1, 7.1.1, 7.1.2

Operating system(s): Windows

Reference #: 1446813

Modified date: 08 May 2013

Translate this page: