Disabling XPages if not needed reduces open files and HTTP start/stop time
Daniel Nashed – 29 September 2024 20:50:03
While working on setup automation I often ran into HTTP startup challenges.
It can take up to 40-50 seconds until the HTTP task is started.
If you look at open files, you notice that each thread has more than 70 files open.
This sums up to up quite some files and the HTTP server start/stop time is much slower.
In case you don't use XPages there is a simple switch to disable the XPages run-time and only load the standard Java components.
notes.ini INotesDisableXPageCMD=1
I first had the impression Java in general would cause overhead on start. But my tests drilled down to XPages/OSGI.
Specially when you run a Traveler server, this can cause even more files open. Traveler auto configuration sets the HTTP threads to 400.
But Traveler uses an OSGI servlet. With Traveler you cannot disable the XPages run-time.
It is still a good idea to set the number of HTTP threads on your server to the number of sessions you need for a Traveler server.
If you are running a small server you might want to lower "Number active threads:" in server document.
-- Daniel
Here is the Traveler message when you still disable it. Traveler will not work without it.
Traveler: SEVERE *system Configuration parameter INOTESDISABLEXPAGECMD=1 in the notes.ini file is preventing the Traveler Servlet from starting.
For Traveler to be functional, please remove this parameter. See the Domino Server information center for more information on notes.ini parameters.
- Comments [3]
![[HCL Domino]](../lotus-domino.gif){kind=small}
![[Domino on Linux]](../domino-linux.gif){kind=small}
![[Nash!Com]](../nashcom.gif){kind=small}
![[Daniel Nashed]](../daniel-nsh.gif){kind=small}