Kbase P80773: Client Server connections to the database throwing memory violation (49)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2008 |
|
Status: Verified
SYMPTOM(s):
Memory violation occuring up to twice a day bringing agents down
SYSTEM ERROR: Memory violation. (49)
Always the last AppServer / WebSpeed agent that dies
Once the last agent is trimmed, operations proceed as normal
Disconnecting client <number> of dead server <number>. (2526)
AS CONN Disconnecting from database <database>, user number <usernum>. (9545)
Error <read/writing> socket, ret=<n>, errno=<n>. (778)
Error reading socket, ret=-1, errno=104. (778)
Sometimes happens when a remote batch process running
Sometimes happens when SonicMQ4GL Adapter connections are made
Stack trace from _mprosrv reads:
drSigFatal
<signal handler called>
enssqrm1
enssbuf
ebsdsread
ebsdnext
enssnext
ensanext
nsaloop
Stack trace from _mprosrv reads:
drSigFatal
<signal handler called>
chunk_free
free ()
utfree
enssfmem
ensscls
mdend
FACT(s) (Environment):
Source code been recompiled
Hardware logs investigated
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
Every occurence of these memory violations have been attributed to Client Server ( C/S ) connections to the datbase, in the network layer accessing memory for various reasons.
FIX:
To initially work around this problem, change all client connection processes from client server to shared-memory connections.
Then as the problem is in the network layer, investigations need to be made into the Network Interface Card (NIC), memory and the routing table on this IP address specifically the packet size.