The PPM Server startup script (kStart.sh) contains two JVM parameters. The kStart.sh JVM parameters are -ms1280m and -mx1280m. These specify that the JVM starts up with a heap size of 1280 MB (1.2 GB), and is limited to a maximum heap size of 1280 MB.
These settings are usually sufficient. For sites with heavy usage, however, consider overriding the default maximum heap size using the SERVER_MAX_HEAP_SIZE parameter in the server.conf file. The amount of memory required depends on factors such as cache sizes and number of Oracle connections.
After you first start the PPM Server following an installation or upgrade, the server occupies approximately 750 MB in memory. As you use the product, the cache fills up and the JSPs are loaded into memory. Over time, the system gradually uses more memory. This is normal, and memory usage levels out over time. In most cases, memory usage can increase to a maximum of 1 GB.
If your Java program requires a large amount of memory, you may find that, at some point, the virtual machine starts to throw OutOfMemoryError instances as it attempts to instantiate objects. This can result from your program using more memory than is available. In this case, you can use command-line options to increase the heap size allocated by the Java Virtual Machine (JVM). If not specified, the heap size defaults to 1 MB, and can increase to as much as 16 MB if your program requires more memory. (To set the initial amount of memory allocated for your program, use the -Xms option.)
PS: If the post resolves your issue, please click KUDOS star icon and mark it as Accepted Solution.
IT Governance Professional & PPM Solution Architect
Hello and thank you very much for answering this information is very well but would like to know how to implement it, and the process for increasing dynamic memory size with that parameter. stay on top of your reply thanks
Has anyone been able to find the upper limits of how much memory can be allocated to one node? the JVM is "only" 32 bit and 1280MB seems to be the maximum - can anyone confirm or deny this? (We see alot of heap space errors so i would increase ours if I could).
My understanding is that 1280MB is the maximum with a 32 bit JVM. One reason for adding nodes is to increase the memory available. Also, we bounce all nodes once per month. There appears to be a small memory leak that reduces available memory over time and this is the only way to recover the lost memory.