Kbase P23718: Why are the _mprosrv processes accumulating memory?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/01/2011 |
|
Status: Verified
GOAL:
Why are the _mprosrv processes accumulating memory?
GOAL:
What are _mprosrv processes?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The _mprosrv has three main roles.
1) It is the Broker (listener) which accepts local and remote connections
2) In its role as Primary Broker (listener) it also creates and manages the shared-memory used by the database and all self-service connections.
3) It can run as a sub-process invoked by the broker to handle remote-client connections.
In this 3rd role, the _mprosrv process services queries on behalf of all connected users.
The users may login and logoff but once the _mprosrv has accumulated memory to service a request it does not release the memory because it is not foreseeable if it will need the memory later on.
On Unix, when ps -ef is run, many _mprosrv processes will display -1 as one of the visible parameters. This indicates that this process is functioning as a server for remote client connections.