Kbase P43824: How to troubleshoot _mprosrv runaway process
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
How to troubleshoot _mprosrv runaway process
GOAL:
Problem with runaway _mprosrv
GOAL:
_mprosrv process runaway information
FACT(s) (Environment):
UNIX
Progress/OpenEdge Versions
FIX:
This process will work towards client requests and take resources necessary to finish the required job. The purpose of this solution is to provide a sample to demonstrate how to narrow down a case of excessive use of CPU caused by _mprosrv.
This solution will also provide places to look at on the database to find if the process is running and maybe who is causing the process to be in this state.
The code below executed against sports2000 database from a remote 4GL client will cause excessive CPU usage.
REPEAT WHILE TRUE:
FOR EACH customer:
END.
END.
It is possible to observe server activity from:
1. promon
2. R&D
3. option 2 - Activity Displays
4. option 2- Servers
5. Look for the value changes on the "Total" column, by entering U to refresh. If the values are changing it means the _mprosrv is processing information.
The next step is to identify users connected to this process.
Through promon option 1 -User Control
than 1- Display all entries. It is possible to identify the runaway process by its PID. The users connected to this server will carry on the server number on the srv column. After identifying the users connected to that server, start disconnecting one by one (Careful with this step sometimes it is .not possible to disconnect a user from the database. The user might be doing something important and it will not be good to disconnect it at will) always observing the CPU usage. When the CPU drop occurs that is the user to be investigated. Check with the user and the application developer what the code is doing..