RegisterLog In to Jazz.net dW

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

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

Follow this link to see the Rational DOORS Next Generation 4.0.4 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

This problem occurs when an artifact has links to other applications, such as References links or Derives links. When you click Properties > Links, the artifact's links are not displayed.

Workaround

To view the artifact's links, use the web client.

Related information

Return to the top of the page


Workaround summary

Problem

Shortly after you start the Requirements Management (RM) server or during an online upgrade, the server becomes unresponsive and might log out-of-memory (OOM), socket timeout exceptions, or both.

If the server is restarted while there is a large Jazz Team Server indexing backlog, indexing resumes and long-running queries, such as recent feeds, are run. Depending on a combination of factors, such as the repository size, server hardware, and user load, the server might report OOM exceptions in the logs.

OOM exceptions might be displayed on the Jazz Team Server diagnostics page. If the RM indexing backlog is high, a warning message is shown:



The above example shows not only a warning about a high indexing backlog, but also errors stating that Jazz Team Server ran out of memory. Even if you do not see an OOM message, you might notice symptoms indicating that the server is running low on memory. It might take a while before the server actually runs out of memory. To find OOM errors, check the server/logs/jts.log file.

Workaround

Complete an offline reindex. The following steps are based on the steps in "Repository tools command to regenerate indexes," which is linked to in the "Related information" section below.

Workaround for Windows systems:

  1. Make sure that Jazz Team Server and the RM server are shut down.
  2. Open a command prompt and enter these commands:
    cd installation_directory\server\
    repotools-jts.bat -reindex teamserver.properties=conf\jts\teamserver.properties scope=all
  3. Restart the servers.
  4. Check the Jazz Team Server diagnostics page again to verify that the indexing backlog is gone.

Workaround for UNIX and Linux systems:

  1. Make sure that Jazz Team Server and the RM server are shut down.
  2. Open a command line and enter these commands:
    cd installation_directory/server/
    ./repotools-jts.sh -reindex teamserver.properties=conf/jts/teamserver.properties scope=all
  3. Restart the servers.
  4. Check the Jazz Team Server diagnostics page again to verify that the indexing backlog is gone.

Return to the top of the page


Workaround summary

Problem

When you are viewing the history of an artifact that is in a module, if you hover over the revision icon, no revisions are shown. Instead, a spinning icon is displayed.

Workaround

To view the changes to the artifact, click the Audit History tab.

Related information

Return to the top of the page


Workaround summary

Problem

This issue occurs on Google Chrome only. In a module that contains a PDF document, if you click the "Click here to open this resource in place" link, the document does not open. Instead, a blank grey box is displayed.

Workaround

Complete these steps:

  1. In the URL bar of Chrome, enter about:plugins.
  2. Next to Chrome PDF Viewer, click the disable link.

Related information

Return to the top of the page


Workaround summary

Problem

In a module, if you search by using the Module Find window, the artifacts that match the search string might not be found. This issue can occur if the search string is composed of all special characters; for example: '(?)'. Searching for those types of strings is not supported. Special characters include: ( ) { } [ ] ? ? / \ : ; * ? ! _ - " < > | & . , ' " #

Workaround

If your search string must include special characters, add alphanumeric characters to the string.

Related information

Return to the top of the page


Workaround summary

Problem

When a report is generated in Microsoft Word and your default browser is not Internet Explorer, any links in the report will not open. This issue is a Microsoft Word limitation.

Workaround

A workaround is published in this Microsoft article: Error message when clicking hyperlink in Office: "Cannot locate the Internet server or proxy server"

Related information

Return to the top of the page


Workaround summary

Problem

When you upload and insert an image into an artifact, the image is uploaded to the project, but an error occurs and the image is not inserted into the artifact. This issue is caused by a change to the insertion logic of the upload window.

Workaround

You can work around this issue in either of two ways:

  • Before you insert the image into the artifact, upload the image into the project.
  • If you try to upload and insert the image and an error occurs, go to the folder that contains the uploaded image and refresh the folder's content. Then, open the artifact and insert the image.

Related information

Return to the top of the page


Workaround summary

Problem

When you use Internet Explorer 8 or a release of Safari 5.1 to download a file that contains Unicode characters in its name, those characters are not shown in the downloaded file name. For example, if you download a PDF document that contains Japanese characters in its name, those characters are not shown in the downloaded file name.

Workaround

Use Safari 6 or later, or Internet Explorer 9 or later.

Related information

Return to the top of the page


Workaround summary

Problem

This problem occurs when you use the web server plug-in for IBM WebSphere Application Server, fix packs 6.1.0.45, 7.0.0.25 - 7.0.0.29, or 8.0.0.4 - 8.0.0.7. When a query times out, this generic server error might be displayed:

500 Internal Server Error.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

Instead of that generic server error, this warning message should be displayed:

The list of artifacts cannot be displayed.
ID CRRRW7611W The server was unable to generate the list of artifacts in a reasonable period of time. Try making the filter more specific. For example, specify which artifact types to display, and try to open the list again.

Workaround

Complete one of these steps:

Return to the top of the page


Workaround summary

Problem

This problem occurs when you try to create an artifact that is based on another artifact that has not been saved. In a module, if you press Ctrl + Enter to create several similar artifacts in succession, the artifacts are not saved when you refresh the page.

Workaround

Complete these steps:

  1. After you edit a newly created artifact in the inline editor, click outside of the editing area so that the editing area loses focus and the artifact is saved.
  2. Click the artifact and press Ctrl + Enter to create another 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


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

When you run a quick search query or term lookup that includes one of the following characters, the results are inconsistent: ( ) { } [ ] ? ? / \ : ; * ? ! _ - " < > | & . , ' ".

This limitation is caused by the way that the Jazz Team Server search facility handles special characters.

Return to the top of the page


Limitation summary

Problem

When you search for text in a module, the search results can return up to 1,024 artifacts that match your search query. If more than 1,024 artifacts in a project match your search query, your search results might be inaccurate.

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


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