Troubleshooting memory issues for IBM Business Process Manager servers
If you are using IBM® Business Process Manager with a 32-bit operating system or Java Virtual Machine (JVM), you might notice issues with server performance and availability, including OutOfMemory exceptions. These happen when the operating system or JVM does not have enough accessible memory to support all the running processes.
If the server performance is severely degraded or if you see an OutOfMemory exception, consider switching to a 64-bit operating system or JVM. Otherwise, use the information in the following table to identify possible solutions for specific memory issues.
Observed behavior | Possible actions |
---|---|
Severely degraded server performance (swapping occurs) |
|
Severely degraded server performance (no swapping) combined with excessive garbage collection activity |
For more information on tuning the heap size and garbage collection settings, see Tuning the IBM virtual machine for Java and Java virtual machine settings. |
Memory issues; for example, the instance occupies much of the available memory | Reduce the branch context cache size. Reducing the cache size from 64 to 16 makes a huge difference in the amount of memory the instance uses, although you are trading off some performance for the improvement in memory use. To change the cache size, locate the 00static.xml file in PROFILE_HOME\config\cells\cell_name\nodes\node_name\servers\server_name\process-server\config\system. In it, you can edit the value for branch-context-max-cache-size. |
An OutOfMemory exception |
|
An OutOfMemoryError exception with a corresponding thread hung exception | If you encounter this particular OutOfMemoryError exception,
you may be able to resolve the problem by completing the following
steps:
|