Workarounds: Jazz Team Server problems in Collaborative Lifecycle Management 4.0.6

The following known problems are related to Jazz Team Server in the CLM 4.0.6 release.

Workarounds

The following problems in this release have workarounds:


Workaround Summary

Problem

If the REST API makes numerous calls to retrieve the project history by using increasing page numbers, the calls can exhaust the Java heap space.

Workaround

Complete these steps:

  1. Increase the maximum Java heap size to avoid running out of space. Use the Java -Xmx parameter to increase the heap size.
  2. Reduce the pageNumber or pageSize parameters that are provided to the REST API.
  3. Reduce the number of consecutive calls to the project history API.

You can use any, all, or a combination of the steps to reduce the impact of this problem.

Return to the top of the page


Workaround summary

Problem

Workaround

Complete these steps:

  1. Save the content in the rich-text editor before you navigate through the browser history.
  2. Avoid using keyboard combinations or shortcuts to navigate in the rich-text editor. Instead, use the mouse or the arrows keys to navigate in the rich-text editor.

Related information

Return to the top of the page


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 0 people rated this as helpful.