Kbase P142261: Progress client getting Memory Violation (49) starting with no procedures and no database connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/03/2009 |
|
Status: Unverified
SYMPTOM(s):
Progress client getting Memory Violation (49) starting with no procedures and no database connection specified.
Memory violation. (49)
Error occurs for one user login but not another.
Error started at specific day and time.
FACT(s) (Environment):
Red Hat Enterprise Linux 5.0
Progress 8.x
Progress 9.x
OpenEdge 10.x
CHANGE:
Memory limit imposed on user level.
CAUSE:
A soft / hard memory limit can prevent Progress / OpenEdge from launching.
FIX:
On RedHat Enterprise Linux check the /etc/security/limits.conf
To see if any specification of soft or hard memory limit for the item "data".
Check if limitations were imposed on user or group for data .
While it is possible to impose a limit, it is dangerous to do so without extensive testing.
All sections of the code must be run within one session to see what the maximum memory used by the client could be with the largest possible range for all variable testing.