Parameter:
HTTP_MaxActiveThreadsShort description: Maximum number of active HTTP worker threads on the Domino web server.
Profile
Parameter | HTTP_MaxActiveThreads |
Category | HTTP / Web |
Component | Server |
Available since | R5 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5 |
GUI equivalent | Server document (Internet Protocols → HTTP → Basics) |
Possible values | Integer 1–999, default 40 (recommended 40–200 depending on load) |
Description
HTTP_MaxActiveThreads defines how many HTTP requests the Domino web server may process concurrently. If the available threads are not enough, additional requests are placed in a queue – visible as rising response times in the browser.For pure XPages/Verse servers, raising the value pays off; however, each thread requires about 10–20 MB of additional JVM memory, so the value must always be chosen in proportion to
HTTPJVMMaxHeapSize and the available RAM.Example configuration
HTTP_MaxActiveThreads=80 HTTPJVMMaxHeapSize=2G
Notes & pitfalls
- The default of 40 is usually too small for heavily used XPages applications.
- Higher → more RAM required by the HTTP/JVM process.
- Can also be set identically in the Server document –
notes.iniwins if present.
- Monitoring:
show stat Domino.Workers.*,show stat HTTP.*.
- Reverse proxy / LB connections (keep-alive) count per open connection – size up if needed.
- The change only takes effect after a restart of the HTTP task.