Workarounds and Limitations: Known issues in Rational DOORS Next Generation 6.0.1
The following known problems are related to the IBM Rational DOORS Next Generation 6.0.1 release.
Upgrading from a version 5 release
For details about known issues that relate to upgrading Rational DOORS Next Generation from a version 5 to a version 6 release, including specific defects and fixes, see the IBM Rational DOORS Next Generation 6.x migration defects Flash article from IBM Support.
Workarounds
The following problems in this release have workarounds:
- WebSphere Application Server stops responding and logs an out-of-memory error
- The server is slow to respond after a new stream or baseline is created
- Comments widget on a personal dashboard displays an incorrect label for the Configuration setting
- Module content is missing in Jazz Reporting Service reports that have a “Lifecycle Query Engine using Configurations” data source
- Project templates cannot be created if the user creating the template has used personal tags
- During the CSV import process, artifacts that were partially removed cannot be reinserted into a module
- Page Up and Page Down keys do not work when you edit an artifact in a module in Mozilla Firefox
- Report Builder might not show the correct artifacts when multiple RM servers with different contexts are registered to LQE
- Report Builder reports and LQE queries might show incorrect link validity status when using the query provided in IBM Knowledge Center
- In Rational DOORS Next Generation, if you use Internet Explorer 11 and use an input method editor (IME) to edit artifacts in modules, unexpected results occur. For example, unwanted text characters are entered.
- Large change set deliveries on DB2 databases might fail with an SQL error
- The Alt+e keyboard shortcut does not insert the euro sign in the Module editor
- Anchor point connections cannot be changed by using keyboard shortcuts on a Turkish Q keyboard
- Table cells are pasted incorrectly from Microsoft Word when “Repeat as header row at the top of each page” is selected
- Links between artifacts in Rational DOORS 9 and Rational DOORS Next Generation do not work as expected when configuration management is enabled
- During an upgrade, the CRJAZ0554I timeout error might occur
- Concurrent changes to an artifact can cause version issues in configurations
- In some browsers, images cannot be pasted from the clipboard into an artifact
- Modules imported into a change set using ReqIF, discarded, and then reimported cannot be delivered
- Text in the editor might be displayed in a language that is not installed
- Rational RequisitePro baselines cannot be imported
- Link columns might not display links if the link type has a URI defined
Limitations
The following problems in this release do not currently have workarounds:
- Microsoft Visio VDX and VSDX file formats have limited or no support for uploaded file previews
- Revision history of an artifact doesn’t show baseline icons
- Errors are displayed during TRS rebase operations if timeouts occur
- Graphical artifacts cannot be opened in version 6.0 or 6.0.1 if the server was renamed
- Artifact changes are delayed in TRS change logs for large projects that are enabled for configuration management
- RM modules cannot be duplicated if they contain a Validated By link to a QM resource
- Comparison wizard does not display artifact content for modules after a server rename
- Opening a module row for editing temporarily shifts content below the row
- Setting a link as valid in Design Management does not change the link status in the RM application
- Changes made to artifacts or comments do not appear in a change set
- Quick Search results do not correctly include artifacts that have a format of Diagram
- If PDF documents are viewed in Microsoft Internet Explorer, the PDF document might hide menus or controls
- Module baselines were replaced with project baselines
- ReqIF import feature does not support importing data into multiple configurations of a project
- A module cannot have multiple templates
- The number of a tags for a project is no longer visible
- Text searches do not support queries that include certain characters
- Large ReqIF files or Rational DOORS migration files cannot be imported into Rational DOORS Next Generation
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
Problem
When Tracked Resource Set (TRS) 2.0 is enabled and you create a new stream or new baseline in a project that is enabled for configuration management, you might experience poor server performance. Both operations initiate background processing that can take an hour or longer to complete for large projects with configuration management capabilities.
Workaround
Disable TRS 2.0 or schedule the creation of streams and baselines during off-peak hours.
To disable TRS 2.0, complete the following steps:
- In a web browser, navigate to https://RM_server:9443/rm/admin#action=com.ibm.team.repository.admin.configureAdvanced.
- In the section named com.ibm.rdm.fronting.server.util.ConfigImpl, find the property named Enable TRS 2.0 service.
- Change the value to false.
- On the right side of the com.ibm.rdm.fronting.server.util.ConfigImpl section title, click the Preview link.
- At the top of the page, click Save.
- For the change to take effect, restart the server.
Related information
Workaround summary
Problem
If a personal dashboard is migrated from version 6.0 or an earlier release to version 6.0.1 or later, and it contains a Comments widget for a project that is enabled for configuration management, the label for the Configuration setting is displayed as “$viewlet.prefs.configuration” instead of “Configuration.”
Workaround
Delete the Comments widget from the personal dashboard and then add it again.
Related information
Workaround summary
Problem
When changes are made to a module in a Rational DOORS Next Generation project that has the configuration management capabilities enabled, issues might occur with reporting on the module’s artifacts in Jazz Reporting Service. Specifically, the “Uses” traceability links do not return any requirements in the context of any configuration except for the one where the changes are made. The same problem can occur when a module is deleted.
Workaround
To restore module content in reports, perform a full rebase of Tracked Resource Set (TRS) 2.0 in Rational DOORS Next Generation and reindex the “TRS 2.0 for DNG Resources” data source in Lifecycle Query Engine.
To avoid the problem in the future, disable the deletion of unused versioned resources in TRS 2.0. Note: Disabling the deletion of unused versioned resources in TRS 2.0 considerably increases the number of resources in the TRS 2.0 change log.
To disable the deletion of unused versioned resources in TRS 2.0, complete the following steps:
- In a web browser, navigate to https://RM_server:9443/rm/admin#action=com.ibm.team.repository.admin.configureAdvanced.
- In the section named com.ibm.rdm.fronting.server.util.ConfigImpl, find the property named Delete unused versioned resources in TRS 2.0.
- Change the value to false.
- On the right side of the com.ibm.rdm.fronting.server.util.ConfigImpl section title, click the Preview link.
- At the top of the page, click Save.
- For the change to take effect, restart the server.
To perform a TRS 2.0 full rebase and reindex the “TRS 2.0 for DNG Resources” data source in Lifecycle Query Engine, complete the following steps:
- In a web browser, navigate to https://RM_server:9443/rm/admin#action=com.ibm.rdm.fronting.server.web.trs.
- Click TRS 2.0 Full Rebase.
- Wait until the process is complete.
- Navigate to https://LQE_server:9443/lqe/web/admin/data-sources.
- Find and click the https://RM_server:9443/rm/trs2 data source (usually named TRS 2.0 for DNG Resources).
- Click Reindex.
Related information
Workaround summary
Problem
Project templates cannot be created properly if the user creating the template has used personal tags in the project. In this situation, no errors are displayed when the project template is created or when a new project is created from the template. However, random artifacts will be missing from the folder view in the new project. Shared tags do not cause this problem.
Workaround
Complete either of these steps:
- Locate a user account, such as an administrative account, that does not use personal tags. Create the project template by using that account.
- If no such user account exists, create a new user account and make it a member of the project. Create the project template by using that account.
Related information
Workaround summary
Problem
When you import CSV files, you cannot reinsert an artifact into a module if the artifact was partially removed; that is, the base artifact reference still exists in the project. The import process is only intended for creating new entries or for updating attributes for an artifact that is already part of the module.
Workaround
To reinsert an artifact into a module, use the artifact grid in the web client.Related information
Workaround summary
Problem
In Mozilla Firefox, when you inline edit artifact content in a module, the Page Up and Page Down keys do not work.
Workaround
Use these techniques to move the cursor:- Use the Up Arrow and Down Arrow keys to move up or down.
- Press Ctrl+Home and Ctrl+End to move to the beginning or end of the text.
Related information
Workaround summary
Problem
When multiple Requirements Management (RM) servers are registered to the same instance of Lifecycle Query Engine (LQE), and the public URLs for the RM servers do not use the same context (such as /rm), Report Builder might not show artifacts or might show duplicate instances of artifacts. For example, these issues might occur:
- Requirement shapes might not be present in Report Builder for some of the RM servers
- Requirement shapes might be listed multiple times, which makes it hard to determine which one to select
Workaround
Set the same context (such as /rm) on each RM server. This action requires a server rename. For details, see the server rename documentation. After the server rename, you must perform a full TRS 2.0 rebase to add the DNG Resources data source back to LQE.Note: This workaround does not apply to RM servers that use different contexts but use the same host name and port to differentiate the public URIs. For example, this workaround does not apply if two servers are identified as https://rm.server.com/rm and https://rm.server.com/rm2.
Related information
Workaround summary
Report Builder reports and LQE queries might show incorrect link validity status when using the query provided in IBM Knowledge Center
Return to the top of the page
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
Problem
The Microsoft Visio file formats that are XML-based, such as VDX and VSDX, lack support for uploaded file previews. For example, the VDX format has no support for file previews. A possible workaround is to convert the file to a different, older Visio format such as VSD, if such a plug-in exists. VSDX files have limited support for file previews; they cannot be rendered as thumbnail images. This means that a preview is not available when embedding the file as an artifact, when performing rich hover, when viewing it in a module, or from reports on that artifact. The only support for VSDX files is for viewing the artifact in full-screen mode or directly opening the artifact in Microsoft Internet Explorer with the Visio plug-in installed.
Related information
Limitation summary
Problem
Before the 6.0 release, the Revision history feature showed icons across the timeline that represented both the revisions of an artifact and any project baselines that were captured with that artifact. In 6.0, the baseline icons are not shown. The revision icons remain and enable you to reach any of the revisions of the artifact.
Related information
Limitation summary
Problem
If you perform a Tracked Resource Set (TRS) 1.0 or TRS 2.0 rebase operation on a large Rational DOORS Next Generation repository, you might receive an error stating that the rebase operation could not be completed successfully. The error does not always mean that the rebase operation failed. In some cases, the error is caused by a timeout. To examine the actual status of a rebase operation, navigate to https://RM_server:9443/rm/trsstatus in a web browser.
Related information
Limitation summary
Problem
If a server was renamed in any release, graphical artifacts cannot be opened in version 6.0 and 6.0.1.
Related information
Limitation summary
Problem
When changes are made to artifacts in a large Rational DOORS Next Generation project that has the configuration management capabilities enabled, delays might occur before the changes appear in the Tracked Resource Set (TRS) 1.0 and TRS 2.0 change logs. As a result, the changes are also delayed for Lifecycle Query Engine reports in Jazz Reporting Service.
Related information
Limitation summary
Problem
If a Requirements Management (RM) module contains a Validated By link to a Quality Management (QM) resource, when you attempt to create a duplicate of the module, the system stops responding while it displays the Copying artifact... message.
Related information
Limitation summary
Problem
After a server rename operation, the comparison wizard does not display the artifact content for module versions that are being compared. The comparison wizard is used during deliver operations to show differences between two versions of a module. If the server was renamed, the wizard shows no content for both versions of the module with artifacts, so the versions cannot be accurately compared.
Related information
Limitation summary
Problem
In Rational DOORS Next Generation 6.0.1, when you open a module row for editing, the rows below the target row temporarily move up and then quickly shift back down to their original position when the row is placed into edit mode.
Related information
Limitation summary
Problem
In Rational DOORS Next Generation 6.0.1 projects that use link validity, you cannot view or set proper link validity information to artifacts in an environment with Design Management 6.0.1. The status that is set in either application is only visible in the application where it is set.
Related information
Limitation summary
Problem
When you work in a change set in Rational DOORS Next Generation 6.0 or 6.0.1, changes made to artifacts or comments are not reflected in the Recent Requirements or Recent Comments views. The changes only become visible after the change set is delivered.
Related information
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
© Copyright IBM Corporation 2015, 2018
Yes