Apache HTTP Server Version 2.2

Apache > HTTP Server > Documentation > Version 2.2 > Modules

#### Please note

This document refers to a legacy release (2.2) of Apache httpd. The active release (2.4) is documented here. If you have not already upgraded, please follow this link for more information.

You may follow this link to go to the current version of this document.

# Apache MPM beos

Available Languages: de | en | es | ko

Description: | This Multi-Processing Module is optimized for BeOS.
Status: | MPM
Module Identifier: | mpm_beos_module
Source File: | beos.c

### Summary

This Multi-Processing Module (MPM) is the default for BeOS. It uses a single control process which creates threads to handle requests.

### Directives

### See also

- Setting which addresses and ports Apache uses

- Comments

## MaxRequestsPerThread Directive

Description: | Limit on the number of requests that an individual thread will handle during its life
Syntax: | `MaxRequestsPerThread number`
Default: | `MaxRequestsPerThread 0`
Context: | server config
Status: | MPM
Module: | beos

The `MaxRequestsPerThread` directive sets the limit on the number of requests that an individual server thread will handle. After `MaxRequestsPerThread` requests, the thread will die. If `MaxRequestsPerThread` is `0`, then the thread will never expire.

Setting `MaxRequestsPerThread` to a non-zero limit has two beneficial effects:

- it limits the amount of memory that a thread can consume by (accidental) memory leakage;
- by giving threads a finite lifetime, it helps reduce the number of threads when the server load reduces.

### Note:

For `KeepAlive` requests, only the first request is counted towards this limit. In effect, it changes the behavior to limit the number of connections per thread.

Available Languages: de | en | es | ko

## Comments

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.