Kbase P143242: Memory violation under heavy load
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  3/24/2009 |
|
Status: Unverified
SYMPTOM(s):
Memory violation under heavy load
SYSTEM ERROR: Memory violation. (49)
free_mem from ld-linux.so.2
nsaloop from _mprosrv
Stack trace from _mprosrv reads:
#1 [0x8181c43] uttraceback+0x37 from /usr/dlc/dlc101b/bin/_mprosrv
#2 [0x8183a58] uttrace+0xd4 from /usr/dlc/dlc101b/bin/_mprosrv
#3 [0x818396b] utcore+0xe3 from /usr/dlc/dlc101b/bin/_mprosrv
#4 [0x805792f] drexit+0x3eb from /usr/dlc/dlc101b/bin/_mprosrv
#5 [0x8095cbc] drSigFatal+0x6c from /usr/dlc/dlc101b/bin/_mprosrv
#6 [0xffffe500] free_mem+0x8095900 from /lib/ld-linux.so.2
#7 [0x8170bbd] nsaloop+0x621 from /usr/dlc/dlc101b/bin/_mprosrv
#8 [0x8092684] doserve+0x464 from /usr/dlc/dlc101b/bin/_mprosrv
#9 [0x8092206] main+0xda from /usr/dlc/dlc101b/bin/_mprosrv
#10 [0xf7dfd87c] __libc_start_main+0xdc from /lib/libc.so.6
FACT(s) (Environment):
Database startup parameter contain: -Ma 400 -Mi 400 -n 400
OpenEdge 10.1B
Linux
CAUSE:
Bug# OE00148720
CAUSE:
Occurs with high client concurrency level on a single server
FIX:
Upgrade to OpenEdge version 10.1C01 or higher.
The workaround is to set -Ma 255 so no server has more than 255 clients at any time.