Workarounds: Web client and server problems in Rational DOORS Next Generation 5.0.2
The following known problems are related to the web client and server in the Requirements Management application 5.0.2 release.
Workarounds
The following problems in this release have workarounds:
- Workarounds and limitations related to uploaded file previews
- Deleting a folder that has modules in its subfolders results in an error
- The login window enters a loop when you try to view links
- When you upload an artifact, a 500 CRRRW7230E error might occur
- Selecting a custom context root for the RM application at install time fails to update RM teamserver.properties file
- An error occurs when you run the clm_undeploy.py script
- WebSphere Application Server stops responding and logs an out-of-memory error
- When you upgrade Rational DOORS Next Generation to a release of 5.0.x from a release of 4.0.x, the 4.0.1 token, floating, and authorized user licenses are not automatically upgraded
- An extra carriage return is added between each module artifact when you create a document-style report for modules
- In a module, pressing Ctrl+Enter quickly in succession results in unsaved artifacts
- On Internet Explorer 11, using an input method editor (IME) to edit artifacts in modules creates unexpected results
- Some non-English fonts cannot be saved or rendered in graphical artifacts
- Rational RequisitePro baselines cannot be imported
- Licenses are not released when you log out
- When you run the setup wizard on Internet Explorer 10, the Finalize Application page for the RM application is blank
- When you delete cells from a table, other content is also removed
- Artifacts in a module might be incorrectly shown after you cancel the edit of a new artifact row
- The graphical editor add-on installer opens when the add-on is installed and disabled
- On Solaris and Linux systems, the Express setup wizard fails when finalizing the RM application
- Link columns might not display links if the link type has a URI defined
- After the RM server is started or during an online upgrade, server problems occur
- PDF documents cannot be viewed in modules on Google Chrome
- Links in reports that are generated in Microsoft Word format do not work
- Unicode characters are removed from downloaded files on Internet Explorer 8 and releases of Safari 5.1
- Timed-out queries might return a generic server error when you use the web server plug-in for WebSphere Application Server
- The Requirements View dashboard widget does not correctly paginate when a lifecycle status filter is applied
- In PDF reports, non-English and ideographic characters are not printed
- When printing reports, the page size for PDF documents cannot be changed
- When you upgrade to 4.0.3, you can save disk space by deleting the converter cache
- During the import of a CSV file that includes a FEAT requirement, a validation error occurs
- Automatic synchronization of artifact content and content in Name field
- Custom Word templates are not updated in an upgrade
- After a document is imported into a module, images that are in headings are not shown in artifacts
- During an import, the wizard might not detect images or text.
- After you save selected text as a new artifact, when the new artifact is linked to or inserted, an error occurs
- The thumbnails of screen flow artifacts are not always rendered in reports
- HTTP requests are not automatically redirected to HTTPS
- When the import wizard extracts requirements from a document, an error occurs
- A CRRRW8010E error occurs when you try to view a graphical artifact
- After a successful upgrade, the upgrade console incorrectly indicates that the upgrade failed
- If the server crashes or is improperly shut down, the server indexes can become corrupted
- Graphical artifacts that are embedded into text artifacts are not displayed in the requirements specification report for Rational Reporting for Document Generation
- Graphical artifacts might be clipped when printed from a browser
- Graphical artifacts cannot be printed by using the browser print function
- In rich text documents, space cannot be added between consecutive tables
- Text is displayed in multiple languages
- On Linux systems, the Rational Requirements Composer server does not start in console-only mode
- The Cut, Copy, and Paste editor menu options are disabled
- How to configure PDF output for Rational Reporting for Document Generation
- Long artifact names cause the artifacts to be displayed with their URL
- Importing a ReqPro Project that was integrated with Rational Requirements Composer requires a manual refresh prior to seeing changes
- When an artifact attribute is deleted from an artifact type, artifact exports fail
- The Rational Requirements Composer on-line migration requires a 4.0 RRC Analyst license, and the Jazz Team Server 4.0 read-only mode now supports installing and assigning licenses
- Adding or removing multiple IBM Rational ClearQuest record links from IBM Rational Requirements Composer or IBM Rational Quality Manager artifacts might not update all selected ClearQuest records
- In the Float data type, users cannot enter values of more than three digits after the decimal point
- The creation of the Money that Matters lifecycle sample might fail with a socket timeout
- Error importing large CSV files into Derby
- In environments that use Rational Requirements Composer V3.0.1.3 and earlier and Jazz Team Server V4.0, issues with snapshots occur
- Internet Explorer automatically generates mailTo hyperlinks that might fail the RM XHTML server validation process
- In the rich text editor, the font size of the bullet or number portion of a list cannot be changed
- In rich text documents, space cannot be added between consecutive tables
- Text in the editor might be displayed in a language that is not installed
Limitations
The following problems in this release do not currently have workarounds:
- Imported Microsoft Word tables might be displayed incorrectly if the original borders are misaligned
- A module cannot have multiple templates
- Internet Explorer 11 does not support links between artifacts in the RM application and Rational DOORS
- The report wizard includes irrelevant parameter fields
- Report generation fails when too many artifacts are added to a report
- The Coverage of Requirements by Test Cases Trend report cannot filter the results by requirement type
- The number of a tags for a project is no longer visible
- Reports do not support Unicode Extension-B characters
- Clustered environments only: An HTTP 403 error is displayed when you try to open a module that was created by importing a document with many artifacts
- The import wizard and summary do not correctly display file names that contain non-ASCII characters, such as Japanese and Chinese characters
- Text searches do not support queries that include certain characters
- When you view artifacts in modules, some toolbar icons are no longer shown
- Re-authenticating from the Requirements Management application to IBM Rational System Architect fails
- Modules that are loaded into the data warehouse can contain a maximum of 100 artifacts.
- The Module Find operation does not account for language sensitivity when searching text
- Collections can no longer contain other collections
- Large ReqIF files or Rational DOORS migration files cannot be imported into Rational DOORS Next Generation
Workaround summary
Workaround summary
Problem
When Rational DOORS Next Generation is deployed on IBM WebSphere Application Server and the folder to delete, or one of its subfolders, contains modules and the module artifact folders, this error occurs:
CRRRW7752W Not all of the folder contents could be deleted. Some of the contents might be locked, some of them might be used in modules, or you might not have permission to delete them.
Workaround
To avoid this problem, you must delete the modules first.
Complete these steps:
- With no filters applied, select the folder to delete.
- Expand the Filter by Attribute section and click More Attributes.
- For the attribute to filter by, select Artifact format.
- Select Module and click Apply.
- Make sure that all of the modules to delete from the folder are shown.
- Select the modules and delete them.
- Clear the Artifact format filter; then, delete the folder.
Related information
Workaround summary
Problem
While you are working with OSLC links, the login window continuously opens and closes. This problem occurs only when both of these situations are in effect:
- You initially logged in to an application other than the Requirements Management (RM) application at https://server:port/rm.
- The RM project is associated with a project that is in another web application and that does not share Jazz Team Server with the RM application. For example, Rational DOORS Web Access 9 or a CLM product that is on a different Jazz Team Server.
Workaround
This problem occurs because the RM application cannot process OAuth authentication data properly in certain situations.
To avoid this problem, log in to the RM application first by going to https://server:port/rm.
If you are already logged in, log out and then log back in to the RM application directly.
Related information
Workaround summary
This article covers two similar issues.
Problem 1
When you upload an artifact, you might see a 500 CRRRW7230E error from the server. The following error will be logged in the server rm.log file:
Server exception: com.hp.hpl.jena.rdf.model.ResourceRequiredException: "" at com.hp.hpl.jena.rdf.model.impl.StatementBase.mustBeResource(StatementBase.java:149) at com.hp.hpl.jena.rdf.model.impl.StatementImpl.getResource(StatementImpl.java:97) at com.hp.hpl.jena.rdf.model.impl.StatementImpl.getProperty(StatementImpl.java:105) at com.ibm.rdm.fronting.server.services.wrappedresources.internal.WrapperResourceUtil.createModel(WrapperResourceUtil.java:163) at com.ibm.rdm.fronting.server.services.wrappedresources.WrappedResourceService.createPostISR(WrappedResourceService.java:227) at com.ibm.rdm.fronting.server.services.folders.internal.FolderWrappedResourcePostRequest.execute(FolderWrappedResourcePostRequest.java:61)
This problem has been observed only on self-hosted IBM test environments that are running on a milestone release.
Problem 2
When you upload an artifact that is of the Feature type, you might see the CRRRW7230E error from the server. For example:
The file could not be uploaded to the server. ID CRRRW7230E The server request to upload the file to the server could not be completed. _3b is undefined _36@https://server:9443/rm/web/_js/?include=A~&etag=CsVhitlSjJh_en_US&_proxyURL=%2Frm&ss=FPDJf&locale=en-us:47773:1 _8@https://server:9443/rm/web/_js/?include=A~&etag=CsVhitlSjJh_en_US&_proxyURL=%2Frm&ss=FPDJf&locale=en-us:6010:1
This problem has been observed only on projects that were initially populated by using the Use Case Requirements predefined template. If you reuse the Business Priority attribute, you might see a similar issue with other artifact types.
Workaround for problem 1
The cause of the problem is bad data in the artifact type that is selected for the upload. Because only some of the artifact types are affected, a simple workaround is to upload by using a different artifact type.
Complete these steps:
- Log in to the Requirements Management (RM) application as a user who has permissions to save and modify types in the project where the problem is occurring. Typically, that user is an administrator of the project.
- Open the project that the issue is occurring in.
- From the Administration menu in the upper-right part of the banner, click Manage Project Properties.
- Click the Artifact Types tab.
- For all artifact types that experienced issues with the upload, follow these steps:
Tip: If you are not sure which artifact types are affected, follow these steps for all artifact types.
- Change the description of the artifact type. Save your changes.
- Change the Description back to what it was and save it again.
Workaround for problem 2
The cause of the problem is bad data in the Business Priority artifact attribute of the Use Case Requirements template.
Complete these steps:
- Log in to the Requirements Management (RM) application as a user who has permissions to save and modify artifact attributes in the project where the problem is occurring. Typically, that user is an administrator of the project.
- Open the project that the issue is occurring in.
- From the Administration menu in the upper-right part of the banner, click Manage Project Properties.
- Click the Artifact Attribute tab.
- Select the Business Priority attribute.
- Place your cursor in the Initial Value field and press Delete.
- Click Save.
Related information
Workaround summary
Problem
This issue affects versions 5.0, 5.0.1, and 5.0.2.
When you install the RM application by using IBM Installation Manager, you can select a custom context root for the RM application and any other applications that being installed at the same time. During the installation, Installation Manager patches the selected context root values into several configuration files, but it fails to update the value in the teamserver.properties file for the RM application.
This problem can also occur during a command-line installation. In that case, you might specify context root values in the Installation Manager response file, but the RM context root value is not applied to the RM teamserver.properties file.
Workaround
After the installation is complete, locate the teamserver.properties file for the RM application. For example, if the custom context root that you selected for the RM application was rm1, the location of the teamserver.properties file is /JazzTeamServer/server/conf/rm1/teamserver.properties. That file contains a property setting like this one:
com.ibm.team.repository.db.jdbc.location=conf/rm/derby/repositoryDB
The installer should have updated the path in this property to conf/rm1/derby/repositoryDB. The workaround for this problem is to manually update the property value to change the /rm/ segment to the custom context root that was selected for RM at install time.
Related information
Workaround summary
Problem
When you run the clm_undeploy.py script on a deployment of version 5.0.2, you might see an error message like this one:
WASX7280E: An application with name "admin.war" does not exist.
This error is safe to ignore.
Version 5.0.1 and earlier releases contained an application WAR file named admin.war. In version 5.0.2, the functionality that the WAR file provided was moved, and admin.war is no longer included in the installation. Therefore, if you upgrade from 5.0.1 or earlier to 5.0.2, you must undeploy the 5.0.1 version of admin.war. A 5.0.2 version of that WAR file does not exist.
The clm_undeploy.py script assumes that admin.war was deployed and tries to undeploy it. The undeployment attempt fails on a 5.0.2 deployment because the admin.war file is not present. However, admin.war is the last application that the script tries to undeploy, so all of the necessary undeployment for the other applications has already occurred. Even though the error message is shown, the undeployment actually completed succcessfully.
Workaround
To avoid seeing the error, edit the following line in the clm_undeploy.py script to make it reflect only the applications that are known to be deployed:
apps=["jts","clmhelp","qm","ccm","rm","converter","admin"]
Related information
Workaround summary
Problem
If you use WebSphere Application Server 8.5.5.6 or WebSphere Application Server 8.0.0.11 with Java runtime 6.1.8.4 (Java 6, R1, SR8, FP4), the Requirements Management (RM) server might display this error in the rm.log file: java.lang.OutOfMemoryError: Direct buffer memory::Please use appropriate '<size>' via -XX:MaxDirectMemorySize=<size>. This error is caused by a defect in the Java runtime version 6.1.8.4. To avoid this issue, remain on the previous WebSphere Application Server fix pack level or upgrade to a later WebSphere Application Server fix pack when one is available.
Workaround
Revert your WebSphere Application Server 8.5.5 fix pack level to fix pack 5 or WebSphere Application Server 8.0 to fix pack 10. If you must stay on WebSphere Application Server 8.5.5.6 or WebSphere Application Server 8.0.0.11, edit the JVM arguments using the WebSphere Application Server Integrated Solutions Console as follows:
- In Servers > Server Types > WebSphere application servers, click the server that runs the RM application.
- Select Server Infrastructure > Java and Process Management > Process Definition.
- Select Additional Properties > Java Virtual Machine.
- In the Generic JVM arguments field, remove this argument: -XX:MaxDirectMemorySize=1G
- Save the changes and restart the server.
Note: This argument must be added again as soon as a WebSphere Application Server fix pack with the Java runtime fix is available. In some cases, removing this argument might cause performance issues because of excessive garbage collection.
Related information
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
© Copyright IBM Corporation 2014, 2017
Yes