File descriptor limitation and workaround for Rational ClearQuest Web running on Solaris 10 or later
On Solaris Version 10 and later, 32-bit applications are limited to using a total of 256 file descriptors (0-255). This limitation is inadequate for many IBM Rational ClearQuest operations and features, including the full-text search feature and integrations.
There is a limitation of 256 file descriptors (0-255) for Solaris 32-bit applications, including ClearQuest.
Diagnosing the problem
Check the file limit of a process by using the pfiles command. Any ClearQuest process that is running with an
rlimit (resource limit) of 256 file descriptors will likely have issues related to the limitation described in this technote.
Resolving the problem
If you are running Solaris 10 or later, try deploying the workaround described in Solaris OS Solutions to 32-Bit stdios 256 File-Descriptors Limitation. The article describes how to extend the file-descriptor limit and how to load the supporting system library.
For example, if you have ClearQuest applications (like the ClearQuest Web full-text search feature) or integrations running in separate WebSphere Application Server profiles, then you must add the following commands to the
startServer.sh script associated with each application or integration. The
startServer.sh script is located in the
bin directory of the associated WebSphere Application Server profile:
ulimit -n 8192
If your deployment includes the integration between ClearQuest and IBM Rational ClearCase, or if you are running the ClearQuest Client (based on the Eclipse Rich Client Platform), then you must update the
clearquest script, which is located in the
ClearQuest-Home/bin directory, to include the just-mentioned commands. The
clearquest script is responsible for starting various processes related to ClearQuest.
If Resolution 1 does not fix the problem, then you must upgrade to one of the following ClearQuest versions: 7.1.2.07 or later, or 8.0.0.03 or later.
Then follow the procedure outlined in Resolution 1.