Troubleshooting
Problem
The ClearQuest Web client v7.0.1 and CQ Eclipse clients v7.0.1 and later might fail when used on a Windows 64-bit operating system. The failure can occur because the Java Virtual Machine (JVM) on 64-bit Windows operating system enables the large address space for an application, giving the application more than the default 2 GB of user memory. Starting in v7.1, the ClearQuest Web server architecture has changed such that this issue no longer exists for the ClearQuest Web client. However, the issue still exists in CQ Eclipse clients v7.1 and later, including the Designer.
Symptom
When the ClearQuest Web client v7.0.1 and the ClearQuest Eclipse clients v7.0.1 and later are running on a Windows 64-bit operating system, the JVM detects the presence of a 64-bit operating system and enables the LARGEADDRESSAWARE bit in the application. This bit causes the ClearQuest Web client v7.0.1 to see up to 7 terabytes (TB) of memory. ClearQuest Web client and CQ Eclipse clients are not designed to run with more than 2 GB of memory. Running with more than 2 GB of memory can result in random memory and pointer manipulation failures.
Cause
ClearQuest is not designed to run in a 64-bit memory space. Running the ClearQuest Web client v7.0.1 and ClearQuest Eclipse clients v7.0.1 and later in a 64-bit memory space provided by the JVM can cause pointer manipulation errors.
Environment
Windows 64-bit operating system
Diagnosing The Problem
You might experience random failures of the ClearQuest Web client v7.0.1 and CQ Eclipse clients v7.0.1 and later when running on a Windows 64-bit operating system.
Resolving The Problem
Take the following steps to prevent this problem:
1. Copy the editbin.exe
program from any Visual Studio 2005 or later installation.
2. Run editbin.exe
on the three Java executables. Running editbin.exe
disables the LARGEADDRESSAWARE bit in these JVMs:
a. For the ClearQuest Web client v7.0.1.x and ClearQuest Eclipse clients v7.0.1.x, which each use Java executables:
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files\Rational\Common\Java142_07\jre\bin\java.exe"
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files\Rational\Common\Java142_07\jre\bin\javaw.exe"
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files\Rational\Common\Java142_07\jre\javaws\javaw.exe"
Attention: In some deployments, the Java executables might be in the Program Files (x86)
folder instead of the Program Files
folder.
b. For the ClearQuest Eclipse clients v7.1 and later:
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files (x86)\IBM\RationalSDLC\common\JAVA5.0\jre\bin\java.exe"
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files (x86)\IBM\RationalSDLC\common\JAVA5.0\jre\bin\javaw.exe"
editbin.exe /LARGEADDRESSAWARE:NO "C:\Program Files (x86)\IBM\RationalSDLC\common\JAVA5.0\jre\bin\javaws.exe"
Attention: Do not change any other Java executables. The WebSphere Application Server and IBM HTTP Server (IHS) have their own JRE, which function fine with the LARGEADDRESSAWARE bit.
See http://msdn.microsoft.com/en-us/library/d25ddyfc.aspx for more information about editbin.exe
.
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21330262