CSP Gateway Configuration Guide - InterSystems Documentation

Apache Considerations UNIX®, Linux, and Mac OS X
The most common reason for problems in this area is if Apache has closed (or recycled) a worker process (in the case of
the example: P2). Of course, a process can crash (for example with an access violation/SIGSEGV error) and, in this case,
an error message will probably be reported in the Apache error log.
Apache also, by default, periodically recycles worker processes.
If you use state-aware sessions, configure Apache such that it doesn’t recycle worker processes by configuring the installation
as follows.
• Set the value of MaxRequestsPerChild to zero
• Set the value of MaxSpareThreads to the same value as MaxClients
If, for whatever reason, it is not possible to prevent Apache periodically recycling processes (perhaps as a result of a malfunctioning
module) and state-aware sessions must be used, then an NSD based Gateway configuration can be used. An
NSD-based architecture avoids the problems discussed above because it effectively separates the process management of
the Gateway from the web server. Options for using the Gateway Network Service Daemon (NSD) are covered in later
sections.
150 CSP Gateway Configuration Guide