Workarounds: Jazz Team Server problems in Collaborative Lifecycle Management 4.0.6

Build Basis: Collaborative Lifecycle Management 4.0.6

Workaround Summary

An out-of-memory error can occur in the Java heap if the REST API makes repeated calls to fetch the project history

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.

Related information

• Reported problem: Work item 299827
• Project history REST API
  

Workaround summary

Content in the rich-text editor of a widget is lost when you navigate through the browser history

Problem

If you navigate backward or forward in the browser while you are editing the content in the rich-text editor of widget, the content is lost when the you return to the widget.

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

• Work Item 287823