Question & Answer
Question
Although the steps in this document are correct, it is NOT recommended to have a Java Heap set to larger than 24GB for Planning Analytics 2.0.5 and lower (which uses JRE 7). As of Planning Analytics 2.0.6 and higher (JRE 8), the limit may be increased but not recommend to be set larger than 56GB. The max Java Heap allowed while also maintaining -Xcompressedrefs is 24GB (2.0.5 and lower) or 56GB (2.0.6 and higher).
Disabling -Xcompressedrefs (by using -Xnocompressedrefs) results in additional memory consumption in the JVM. It is instead recommended to have multiple JVMs (TM1 Web Tier installs), than to have one large JVM.
Disabling -Xcompressedrefs (by using -Xnocompressedrefs) results in additional memory consumption in the JVM. It is instead recommended to have multiple JVMs (TM1 Web Tier installs), than to have one large JVM.
This document will remain online however, as it is possible a customer may encounter the scenario described within (unable to start the service) if unaware what increasing the JVM may do, Planning Analytics Local 2.0 uses WebSphere Liberty Profile to run TM1Web, pmpsvc, and the pmhub web applications. Previously, in TM1 10.2 and 10.2.2 Tomcat was used to run these same web applications. Using Tomcat the JVM maximum heap size could be set to 32 GB or higher with no additional configurations changed required.
With WebSphere Liberty Profile an additional change is required to allow the Java process to start with a larger heap size if it exceeds the Xcompressedrefs restriction above. If the additional configuration change is not made the Java process will fail to start and the TM1 Web applications will not be accessible. Cognos Configuration and the Windows services list will still show the IBM Cognos TM1 services as being started.
With WebSphere Liberty Profile an additional change is required to allow the Java process to start with a larger heap size if it exceeds the Xcompressedrefs restriction above. If the additional configuration change is not made the Java process will fail to start and the TM1 Web applications will not be accessible. Cognos Configuration and the Windows services list will still show the IBM Cognos TM1 services as being started.
[{"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Planning Analytics v2.0 - TM1 Application Web","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"2.0.2;2.0.1;2.0","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}},{"Product":{"code":"SSKVSF","label":"Planning Analytics on Cloud"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
09 May 2025
UID
swg22008559