Known issues
Review the known issues for version 7.0.2.
Workarounds
The following issues in this release have workarounds.
ID | Description |
---|---|
460542 | Application menu is empty in the Add Association dialog box First occurrence: 6.0.6 Problem: When you add an association to a project area, the Application menu in the Add Association dialog box might be empty. Typically, this issue occurs if you have several hundred project areas and use Mozilla Firefox as a web browser. Workaround: Complete one of
the following workarounds:
|
488878 | FullTextIndex data is obsolete and needs to be deleted First occurrence: 7.0 Problem: The FullTextIndex analyzers have been updated to generate proper tokens (indexing and searching) for version text.For example, input text "eclipse 4.2.2" generates two tokens: "eclipse" and "4.2.2", instead of four tokens such as "eclipse", "4", "2", and "2". This update requires existing full-text search indexes that were created in previous releases to be rebuilt. Workaround: The Engineering Workflow Management (EWM) client for Eclipse IDE maintains a local full-text search index in the .metadata/.plugins/com.ibm.team.fulltext.client/fulltext_index folder in each Eclipse workspace. When you upgrade the EWM client for Eclipse IDE to 7.0, make sure you delete that folder in each workspace before you run the upgraded version of EWM. |
418365 | Global Configuration Management custom attributes and links are editable by default after
upgrading from a pre-6.0.4 release First occurrence: 6.0.4 Problem: In Global Configuration Management version 6.0.1, 6.0.2, and 6.0.3, custom attributes and links of baselines are read-only in the web client. If you upgrade from one of these releases to version 6.0.4 or later, the attributes and links are editable by default after the upgrade. Workaround: If you prefer custom attributes and links of baselines to remain read-only after the upgrade, go to Manage Project Properties and clear the Allow editing on baselinescheck box for each item. |
447837 | Licensing errors might occur if you upgrade the Java environment or upgrade applications to
version 6.0.5 or later First occurrence: 6.0.5 Problem: If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 and later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java. For example, the License Key Management page for Jazz Team Server might display the
following error in the Description field: The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys. Workaround: The licenses in the IBM Rational License Key Center were updated to use a different signature algorithm. After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses. Important: If you are not upgrading all applications at the same time, you must apply an
interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The
following interim fixes contain the compatible version of Java:
If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues. To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license: For term (floating or authorized user) or token licenses: Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have
to download the license.dat file because it does not contain changes.
For non-term floating and authorized user licenses:
Note: If you imported trial licenses before the newer versions of Java were adopted, you might still
receive errors in the jts.log file even after you import the updated licenses.
For example, you might receive this error:
CRJAZ0965I The file was not a valid server or
client access license activation key . You can ignore these errors. |
494174 | Long response time for editing project areas with large numbers of project
associations First occurrence: 6.0.1 Problem: If you have a large number of project associations in a project area, selecting "Edit project area" in the web client kicks off a service on the JTS that can run for many hours. If you try to execute it again after the service times out, several processes run again and reduces the performance of the server as they use up all of the available CPU. Workaround: There are two potential workarounds:
|
511213 | The clmhelp.war file and the updateSite.zip for release 7.0.2 are unavailable for
download First occurrence: 7.0.1 Problem: The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download due to technical issues. Workaround: You can install the KCCI.zip file on your intranet server to view the help locally. Click here to download the ELM702_KCCI_contents.zip file. For information about installing the KCCI.zip file, see the Installing help on an intranet server topic. |
486186 | Tomcat is no longer supported as an application server First occurrence: 7.0 ProblemStarting in Engineering Lifecycle Management (ELM) V7.0 release, Tomcat is no longer supported as an application server. For details on the support and planning notes, see Support and planning notes. Workaround: When upgrading a Tomcat-based deployment to an ELM V7.0 (or later), you must base the new deployment on WebSphere Application Server or WebSphere Application Server Liberty Profile. The Interactive Upgrade Guide generates instructions for migrating from Tomcat to Liberty Profile. Migrating to a WebSphere Application Server profile must be done manually. The command options related to migrating to a new Tomcat installation are
removed from the upgrade scripts and the repository tools migration commands. The following attributes
are no longer supported, and result in errors if you use them:
Tip: For upgrade scripts, the attributes require a leading dash such as
-updateTomcatFiles . Whereas, the repository tools migration command is without a
dash preceding an attribute, such as: repotools-<app>
-migration_<app>_updateConfigurationFiles updateTomcatFiles=yes , where
<app> is one of jts , ccm ,
rm , qm , gc , dcc , or
relm . |
496365 | Upgrade to Java 8 SR6 to avoid GPF error during full text reindexing First occurrence: 6.0.6.1 Problem: Release 6.0.6.1 and 7.0 requires rebuilding the full text search indexes. On 64 bit Linux servers, a defect in the IBM Java runtime environment might cause a general protection fault (GPF) during the reindex process. Workaround: When you upgrade to release 6.0.6.1 or 7.0, upgrade the IBM Java runtime environment to IBM Java 8 SR6 (version 8.0.6.0) before you perform the full text reindexing. |