Parameter:
HTTPJVMStackShort description: Stack size per thread for the HTTP JVM – raise it in case of
StackOverflowError in deeply nested XPages/Verse renderings.Profile
Parameter | HTTPJVMStack |
Category | Performance / Memory |
Component | Server |
Available since | 12.0 |
Supported versions | 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | KiB (default 512; typical 512–2048) |
Description
HTTPJVMStack sets the Java thread stack size (-Xss) for the HTTP JVM in KiB. This JVM hosts XPages, servlets, OSGi plug-ins, and the Domino REST API. With deeply nested XPage components, complex JSF trees, or recursive custom controls, the default stack can be too small – the JVM responds with java.lang.StackOverflowError or aborts the request hard. A moderate increase (e.g. to 1024) resolves these cases without dramatically raising the HTTP process memory footprint.Example configuration
HTTPJVMStack=1024
Notes & pitfalls
- Value in KiB (
1024= 1 MiB per thread).
- More stack × more worker threads (
HTTP_MaxActiveThreads) = noticeably higher RAM usage.
- Takes effect only after
restart task http.
- Don't set it too high:
>4096is usually a workaround for an actual code problem (endless recursion).
- For recurring
StackOverflowError, also analyze heap and thread dumps.