Parameter:
JavaMaxHeapSizeShort description: Maximum heap size of the Java VM that Domino starts for Java agents and HTTP-related Java components.
Profile
Parameter | JavaMaxHeapSize |
Category | Client configuration |
Component | Server, Client |
Available since | 9.0 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document |
Possible values | Memory value including suffix, e.g. 256M, 1024M, 2G |
Description
Java agents, the HTTP servlet engine subsystem, and extensions such as XPages run in a JVM whose heap is limited by
JavaMaxHeapSize. Values that are too small cause OutOfMemoryError in agents or web applications; values that are too large waste RAM and on 32-bit platforms can even cause startup errors. The default is 256M; for production servers with XPages / REST apps, 512M to 2G is common practice.Example configuration
JavaMaxHeapSize=1024M
Notes & pitfalls
- On 64-bit platforms, set the value to ≥
512Mwhen XPages or larger Java agents are used.
- Requires a restart of the consuming tasks (HTTP, AMgr) or a server restart.
- Before changing the value due to memory shortages, measure the actual load using Java profiling / heap dumps.
- The same parameter also takes effect in the Notes Client (e.g. for local Java agents).