RegisterLog In to Jazz.net dW

Workarounds: Web client and server problems in Rational Requirements Composer 4.0.3 and Rational DOORS Next Generation 4.0.3

The following known problems are related to the web client and server in the Requirements Management application 4.0.3 release.

Follow this link to see the Rational DOORS Next Generation 4.0.3 rich client workaround article.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not have current workarounds:


Workaround summary

Problem

When a saved view that contains a lifecycle status filter is displayed on a dashboard in the Requirements View widget, you cannot paginate through the results. If you try to move to the next page, this error message is displayed: CRRRW7558E The server indicates that it does not permit the operation. The message that follows might include additional information about why the operation is not permitted.

Workaround

To work around this issue, complete one of these steps:

  • In the Requirements View widget, change the page size settings so that you can see a maximum of the first 50 results.
  • Open the Artifacts page and run the saved view. On the Artifacts page, you can correctly paginate through the results.
  • On the dashboard, add the Requirements Tracing widget and set the widget to use a similar lifecycle status filter.

Related information

Return to the top of the page


Workaround summary

Problem

When you upgrade to version 4.0.3 from version 3.0.1 or later, the history resource format is migrated to a new, more compact format as users update artifacts in version 4.0.3. If users update many artifacts in a short period, excessive load is placed on the server. This issue occurs especially with modules that contain many artifacts.

The excessive load can cause the server to become unresponsive. This problem is more likely to occur just after the server has been upgraded to version 4.0.3, during an initial period of heavy use.

To determine whether the server is experiencing excessive load due to history migration:

  1. Log in to the Requirements Management (RM) server as a JazzAdmin user at https://rmhost:port/rm/counts.
  2. In the AsyncTasks section, find the MigrateOldChangeLogsToFeed row.
  3. View the Active column and verify whether it shows 10 or fewer active migration tasks. If the column consistently shows more than 10 active change log migration tasks, the migration might adversely affect query performance.
  4. To assess query performance, on Jazz Team Server, check the jts.log file for canceled queries. Canceled queries are indicated by this message: CRJZS5544W.
  5. If the jts.log file indicates canceled queries and the number of change log migration tasks is high, follow the workaround steps.

Workaround

Complete these steps:

  1. Contact IBM Software Support and request the RM change log migration tool.
  2. Restart the Requirements Management (RM) server and Jazz Team Server to ensure that the change log migration and any long-running queries are stopped.
  3. Run the change log migration tool on your RM server by following the instructions included with the tool.
  4. Before you start using the RM server again, wait for the tool to finish running. Depending on the amount of history resources, it might take several hours for the tool to finish. If you use the RM server while running the tool, the server might become unresponsive and the tool might fail.

Related information

Return to the top of the page


Workaround summary

Problem

The performance PDF file does not support non-English and ideographic characters. If those characters are included, information is not displayed in reports.

Workaround

When you print a report, use sophisticated format or Microsoft Word format. Those formats support non-English and ideographic characters, with the exception of Unicode Extension-B.

Return to the top of the page


Workaround summary

Problem

In Internet Explorer 9, when you print a report of an artifact that includes a custom table, the table is not properly displayed in the report.

Workaround

Open and save the artifact in another supported browser, such as Firefox. After you save the artifact, you can print the table by using any browser, including Internet Explorer.

Complete these steps:

  1. Open the artifact in any supported browser except for Internet Explorer.
  2. Click Edit.
  3. Save the artifact without making changes.
  4. Print the report.

Related information

Return to the top of the page


Workaround summary

Problem

When you print a report to a PDF document, the page size cannot be changed. Even if you try to change the size by editing the com.ibm.rdm.fronting.server.publish.PaperSize property, the size cannot be changed.

Workaround

Print to Microsoft Word format, as that format supports changes to the page size.

Related information

Return to the top of the page


Workaround summary

Problem

When you hover over a requirement artifact, the rich hover might display this error message: ERROR 500: Internal Server Error. java.lang.NullPointerException.

Workaround

Complete these steps:

  1. Open the artifact.
  2. In the sidebar, expand the Links section. If you are prompted to log in to an associated project, log in.

Related information

Return to the top of the page


Workaround summary

Problem

The 4.0.3 version of the converter cannot read old cache files. Although new cache files will be created as needed, the old files are not deleted. To save disk space, you can delete the converter cache.

Workaround

Complete these steps:

  1. Find the location of the cache directory:
    • If you are using Apache Tomcat, the default location is JazzInstallDir/server/rrcweb/cache.
    • If you are using IBM WebSphere® Application Server, the default location is ProfileRoot/rrcweb/cache, where ProfileRoot is the root directory of the WebSphere profile that contains the converter application.

    Tip: You can also find the location by going to the converter diagnostic page. With the application server running, go to http://host:port/converter/htmlgen; for example, http://exampleserver:9443/converter/htmlgen. On the page that opens, note the location of the cache directory.

  2. Stop the application server.
  3. Navigate to the cache directory, and then delete all of the files from the directory.
  4. Restart the application server.

Related information

Return to the top of the page


Workaround summary

Problem

If you import a CSV file that includes requirements of the FEAT type, a validation error might occur. This error occurs only on projects that were created by using the Traditional Requirements template.

Workaround

Complete these steps:

  1. From the Admin menu, click Manage Project Properties.
  2. On the Artifact Attributes tab, select the Business Priority artifact attribute.
  3. Make a change and then save it. For example, you might add a description and save it.
  4. Import a FEAT requirement as you normally would.

Related information

Return to the top of the page


Workaround summary

Problem

When you create or edit an artifact, you can type a name for the artifact in addition to the main text content of an artifact. The content that you type in the Name field acts as a title, which identifies the purpose of the artifact.

If the Name field is empty, it is automatically populated from a shortened version of the artifact's text content. If the content of the artifact is later modified, the content in the Name field is synchronized and updated accordingly. However, if the content in a Name field is explicitly set, the automatic synchronization no longer occurs. One situation in which this might happen is if you add an existing artifact into your module and that artifact already has a Name field explicitly set.

Workaround

If the synchronization does not seem to be occurring for a particular artifact, another user might have explicitly set the content of the Name field. To get the synchronization to work again, delete the content in the Name field.

Related information

Return to the top of the page


Workaround summary

Problem

In version 4.0.3, if you get an error or warning message that contains a linked ID, such as CRRRW7321W, when you click the linked ID, the information center opens and displays a "page not found" message. This problem occurs because the messages were recently moved from the product information center to their own information center on Jazz.net.

Workaround

If you get an error or warning message that has an ID, go to the messages information center, and then search for the message ID.

Return to the top of the page


Workaround summary

Problem

After you add an existing artifact to a module, if you try to create an artifact whose type is not the type that is currently set in the blue Create button, a warning message about concurrent access is shown.

Workaround

When the warning message is shown, click Yes. Then, you can create an artifact. The warning message is not shown again unless you try to add an existing artifact.

Related information

Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Limitation summary

Problem

Unicode Extension-B characters cannot be printed in reports in the Requirements Management (RM) application. Artifacts can contain Unicode Extension-B characters, but those characters are not included in printed reports.

Related information

Return to the top of the page


Limitation summary

Problem

In a clustered environment, if you try to open a module that was created by importing a document with many artifacts, an HTTP 403 error is displayed. Also, in the module artifact folder, not all of the imported artifacts are displayed.

If you experience this problem, contact IBM Software Support.

Related information

Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Return to the top of the page


Feedback
Was this information helpful? Yes No 0 people rated this as helpful.