Kbase P150624: Database shuts down when Broker is trying to clean up users associated with the dead server.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/31/2011 |
|
Status: Unverified
SYMPTOM(s):
Database shuts down when Broker is trying to clean up users associated with the dead server.
Users tend to be holding latches associated with Buffer Pool, Hash Table etc.
Database server process, _mprosrv is terminating without reporting errors.
Database serfver process (_mprosrv) is dying periodically.
Disconnecting dead server <number>. (2525)
Disconnecting dead server -1. (2525)
Stack trace from _mprosrv reads:
0x0043E574 _qrTerm+04 (pnode = 01454f52)
0x0043EA41 _qrClearQuery+31 (pqid = 0012f3a0)
0x0043EAEC _qrdlc+0C (pqid = 0012f3a0)
0x004473BB _nsaCursorDelete+1B (01cf6aa8, 01d4406d)
FACT(s) (Environment):
Application code does not make use of AppServers
Clients run code in client/server mode.
Application being used makes use of many persistent procedures.
Windows
Progress 9.1E04 Service Pack
OpenEdge Database Category: Repair
CAUSE:
Too many cursors remaining in memory which results in the server (_mprosrv) terminating because of an overflow.
FIX:
Manage structures being placed in memory and clean up after them as necessary. The solution P124509, "Database log file showing clients being cleaned up after dead server messages." is useful for identification of structures / objects being left in memory.