Fixes Defects: PM57371,PM59071,PM59537,PM60748,PM61242,PM63389,PM65721,PM71158,PM71175,PM72905,PM74119,PM74838,PM76855 This patch contains the following software changes: PM57371: Problem: ClearQuest Eclipse client continues to log into an old database even after it's been moved. Fix: After a database move, ClearQuest Eclipse will log into the new moved database so data is put in the correct place. PM59071: Problem: ClearQuest Web list view control fields have an inconsistent sort order if the unique key field of the reference record is not displayed.  When a CQ Web record with a list view control field is first loaded it is sorted. Refreshing the record sorts the reference list in a different order. Fix: ClearQuest Web list view control fields now sort in a uniform way even if the unique key field of the reference record is not displayed. PM59537: Problem: ClearCase and ClearQuest removed the original MSI packages used to install 3rdParty components, upon cleanning up the Windows MSI cache, the packages had problems to perform Installation Manager Operations. Fix: Updated the ClearCase / ClearQuest to keep a copy of the original MSI packages inside the Install directory in case the machine's MSI cache is cleared, in this situation the MSI system will have the original MSI path and prevent problems on the Installation Manager Operations. PM60748: Problem: By default, after deploying ClearQuest Web on an IBM WebSphere Application Server, the JSESSIONID cookie path is set to the domain root /. If there are other web applications running on WebSphere Application Server that set the JSESSIONID cookie path to /, this creates a JSESSIONID conflict, which causes ClearQuest Web functions to fail. Fix: The ClearQuest Web session id name is no longer hard coded to use JSESSIONID.  If there's a JESSIONID conflict, the ClearQuest Web session id can now be renamed.  The following technote also explains an alternate workaround:  http://www-01.ibm.com/support/docview.wss?uid=swg21595387 PM61242: Problem: Attachments can not be added to a ClearQuest Web record after a user session has timed out.  The record can only be saved without attachments or discarded completely. Fix: After a ClearQuest Web user session has timed out, a relogin dialog appears and attachments can be added to a record. PM63389: Problem: Logging into ClearQuest takes more time now than 7.0.1.x due to changes made to reading and writing database information to the registry. Fix: Database information is now cached in memory to improve ClearQuest logon performance. PM65721: Problem: When a ClearQuest Web record contains a reference list with over 1000 items, any modification on the record will cause unresponsiveness and a "CRVSV0917E The request timed out waiting for a locked resource to become free." error message. Fix: Modifying a ClearQuest Web record with a reference list of over 1000 items now works fine.  The locking condition on the resource mentioned in the message has been eliminated so this error no longer occur. PM71158: Problem: The error "Unexpected character 'xxx'" is intermittently thrown when a ClearQuest Web user adds a child record to a form.  NOTE - this is only a problem with CQ Web 7.1.2.x. Fix: ClearQuest Web has been fixed so this error no longer appears randomly. PM71175: Problem: When a ClearQuest Web CQRPC process reaches the 'Recycle Server Lifetime Limit', it is marked for termination by the CM Server. If the CQRPC process fails to exit, it will appear as hung in the process list and will run indefinitely if not terminated manually. Processes like that can and should be terminated to prevent them from consuming unnecessary resources such as CPU or Memory. Fix: A fix has been made to use a PERL script, called cqrpccleanup.pl, to address this issue. This script is run automatically by the CM Server periodically based on an MBean value cqrpcAbandonedProcessCleanupInterval. The script checks the PIDs of the cqprc processes that are running in CM Server and that are running on the machine itself. It terminates the processes that are not in the CM Server list and that have been up for at least 5 minutes. PM72905: Problem: A ClearQuest security problem was identified. Fix: The ClearQuest security problem was fixed. PM74119: Problem: The Microsoft patch KB2633952-v2 can cause a condition with some eastern Asian timezones where time conversions to GMT are off by one hour in non summer months (months correlated with daylight savings times in other zones where DST is honored).  As example this would convert a Tokyo timezone GMT+8 instead of GMT+9 and since ClearQuest saves dates in GMT these times may be off by one hour.  NOTE - This not a problem with ClearQuest 8.0.0.x. Fix: The ICU libraries used to determine date/time values have been updated in ClearQuest and ClearCase to handle this Windows update. PM74838: Problem: Date field values are not displayed in a query result set if the ClearQuest Web server is on certain non-English operating systems such as German or French. Fix: ClearQuest Web date field values now display in query result sets on all locales. PM76855: Problem: ClearQuest Web users on some non-English locales receive a error message when requesting a date time field using a OSLC request like the following:  "http://9.32.253.123/cqweb/oslc/repo/7.0.0/db/SAMPL/simpleQuery/16777224?oslc.select=cq:Submit_Date" Fix: When calling OSLC requests as in the above example, ClearQuest Web query result sets are correctly displayed on all locales.